I a customerwhich are already using this extension point to migrate their views to the new e4 programming model. I think it is a real nice way to migrate almost painless. The e4 wrapper provide the same functionality but for the customer having this as default option was a big win.
So obviously I would like to keep this option, even if fragment integration is solved. Best regards, Lars 2014-01-29 Wim Jongman <[email protected]> > The e4view extension point forces the customer to code with the model > manually for menus and toolbars instead of getting this from the model. If > the model integration in 3x is complete I am leaning towards +1 for > removing it (not that I have a say). We should not be afraid to give the > early adopters a little bit more work. That is why they are an early > adopter right? Especially when they have a better solution (assuming this > is available of course). > > Not as a hard requirement, but to be really useful in the E3 world, the > "pure e4view" should have the following things: > > 1. The E4 and E3 selection services are not bridged - (would be cool to > fix for M6) > 2. The "pure e4view" is not a first class citizen in the e4 workbench > (quick search??, view menu??, Tom and Paul have given some hints about > this, would be cool to fix for M6 as well) > 3 .. other things?? > > > Cheers, > > Wim > > > > > On Mon, Jan 27, 2014 at 11:50 PM, Lars Vogel <[email protected]> wrote: > >> I think the e4view extension point addition is very useful for customers >> which wants to start a migration. >> >> Best regards, Lars >> >> >> 2014-01-27 Wim Jongman <[email protected]> >> >>> >>> >>> >>>> >>>> *New 'e4' based extension point extensions*: >>>> - We've done the 'e4' view work but it hasn't been tested much >>>> and we're nowhere on either the Commands / Handlers side of things. Not >>>> sure how / if Wim's new 'mixed mode' work affects this... >>>> >>>> Yes, my work could obsolete this extension point. The extension point >>> is working fine btw but it has some drawbacks. See my analysis of the >>> drawbacks here [1] >>> >>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=376486#c32 >>> >>> >>> >>> _______________________________________________ >>> e4-dev mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/e4-dev >>> >>> >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> >> > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > >
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
