Thanks
Mike

Actually I am very aware of Open AT, that was a poor wording on my side to say “Linux [...] the OS that Sierra modules are running”. The plan is to Open Source the set of tools allowing to develop for Linux platforms, since this is where there is the most interest for the M2M community at large. Please also note that there are many things in Koneki that are not directly related to “actual” development, and thus are not really related to Linux, OpenAT, Lua, or whatever: support to manipulate protocols, simulators for client/server communication, utilities to help configure M2M devices, …

I am not sure I understand your concern about Lua support being a restriction?
C development, if this is why your talking about, is of course still possible, we just put a bit more effort on the Lua stuff because it opens the door to great tooling (e.g. LuaRPC to remotely configure the target, Lua packaging mechanism –LuaRocks– to package and provision applications, …)

Thanks very much for your feedback, and I hope I have clarified things

You seem unaware of the Sierra Wireless (formerly Wavecom) Open-AT modules, then?

See: https://forum.sierrawireless.com/viewtopic.php?f=34&t=5472&p=22744

See also: http://tinyurl.com/69r857u

I think the Lua focus will greatly restrict the usefulness at the embedded end – I don’t think that’s a good thing?

Pleine d’espoir … bah non ! elle est plus là la présentation que tu as faite ???

bon bah j’vais chercher …
Bonnes fêtes !

If so, given your vast contributions to Eclipse, may I ask you if UOMo, with a compatibility layer to JScience (unitsofmeasure.org) could be of interest?

Cheers,
Werner

je souhaite utiliser p2 pour distribuer non seulement des plugins/features que je développent mais aussi d’autres choses comme des binaires executables, des msi, … bref des choses qui ne sont ni des plugins ni des features ni des produits. Or je ne sais pas comment faire pour créer un I.U. and des touchpoints permettant de décrire ce qui peut etre installer, mis à jour. Je ne trouve pas trop de documentations ou d’exemples sur le sujet donc je suis preneur pour toute information…
Merci d’avance

P.S. j’avais suivi ta presentation a Eclipse Now You can 2008

I’m new to EMF, PDE and databinding. I’m learning much from this project’s source code.

There is one struggle I have finally overcome. I hope I’m not blowing etiquette by sharing here. Is there a better forum?

I’m probably using the wrong terms as in this description here. I’m describing in terms of the ds implementation as common reference for us to communicate. In reality, I’m working on a different model editor.

ProperiesDetailsPart.bind(DataBindingContext bindingContext) is using return from EMFDetailsPart.getCurrentSelection(). This led me to believe that bind was called after every selection change. In fact, this is not the case. DetailsPart.showPage calls the pages’ createContents method only once (maybe?) per editor instance, and always before it calls the page’s selectionChanged method. So, getCurrentSelection is returns null (or the old selection) when the part’s bind method is called.

This became important to me because some of the features my user would select are not fully built. Some nested features do not exist when the ‘master’ feature is selected. The behavior when this occurs is simple: the user can enter text into a text box in the details side of the page, but the databinding is not effective. The databinding finds the nested feature non-existing and doesn’t add the nested feature or otherwise change the model.

I don’t know if my workaround is the best solution, but I overrode selectionChanged to disable the text fields corresponding to features that do not exist. I think my users will prefer to create those fields explicitly, instead of the editor creating them.

Thanks for your effort.

John

thanks!

Tamar

While looking at your code I don’t see any custom ValidationStatusProviders. All of the calls to DataBindingService.bindValue calls either have null, null for their targetToModel / modelToTarget or they lightly extend the generic EMFUpdateValueStrategy (overriding the convert method)

I also don’t see where ValidatingService35 is called.

Can you please clarify exactly where you are linking the databinding validation with the EMF validation?

thanks much
Tamar

+1

ekke