Good points Veselin, please file a bug for these issues (and ideally provide a patch through gerrit). These will be processed after the move.
On Tue, Dec 23, 2014 at 4:32 PM, Veselin Markov <[email protected]> wrote: > Hello, > > I’ve been working with the e4 model editor for tree moths now and I cannot > imagine editing the e4xmi files any other way. However the editor is > somewhat irritating at least on two places for newcomers. I’m not sure if > this has to be changed before or after the project is moved (if at all) but > I’d like to list my suggestions anyway: > > > > 1. When it comes to fragments it was not clear to me right away, > that “Element ID” was actually a reference to *another’s* element ID and > was not its own ID. > > 2. And lately I had to google a while until I got a parameter of an > “Handled Tool Item” working. It was not obvious to me, that “Name” is an > reference to the ID of a command’s parameter. > > > > In general I’d find some embedded help very good but relabeling a couple > of text inputs will be a good start. I certainly will continue using the > model editor and I believe this sort of changes are surely user friendly > and will ease adoptation. > > > > Greetings > > Veselin > > > > *Von:* [email protected] [mailto:[email protected]] *Im > Auftrag von *Jonas Helming > *Gesendet:* Dienstag, 23. Dezember 2014 15:49 > *An:* E4 Project developer mailing list > *Betreff:* [e4-dev] Split repositories > > > > Hi, > > the restructuring review for moving the core tools to the platform project > has been successfully concluded [1]. > The concrete steps are now tracked in [2]. > The next step is to split the components to be moved into a new repository > [3] and prepare them for the move. > The components to be moved as discussed here [4] are: > > org.eclipse.e4.core.tools.feature - and its contents: > org.eclipse.e4.tools > org.eclipse.e4.tools.compat > org.eclipse.e4.tools.emf.editor3x > org.eclipse.e4.tools.jdt.templates > org.eclipse.e4.tools.services > org.eclipse.e4.tools.emf.ui > > I would like to to do the split and the preparation soon (ideally during > the holidays). However, once I have started the split and before they are > moved and integrated in the platform project, there will be no build and no > new update site for them. Additionally they will be removed from the e4 > project, so the are no longer on the nightly build. > > *IMPORTANT* *QUESTIONS*: > > 1. If you have any open changes or things you think need to be fixed > before the move, please let me know by adding a blocking issue to [3] and > get those changes in as soon as possible > 2. Shall we do another stable tagged build before the move to have a > stable update site with the newest state? => [5] > > Best regards and Merry Christmas! > > Jonas > > > > > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=452693 > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=452061 > [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=455725 > [4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=445742 > [5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=456081 > > _______________________________________________ > e4-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/e4-dev >
_______________________________________________ e4-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/e4-dev
