Kai, I agree 100% that going forward we have to start to converge the e4 and Eclipse 4 stories, breaking down the current boundaries between them. This will mean a number of things:
1) Allowing e4 parts / commands... to be included in a 4.x 'install' directly. This is relatively straightforward but may require some API / Extension changes... 2) Refactoring as many of the existing 3.x bits as we can to work in EAP apps without having to bring in the complete compatibility layer. This will have to be an 'open-ended' activity since how quickly we'll be able to proceed will depend on each bit's current dependency on the Workbench[Window/Page] etc. The splash screen should be one of the easier cases...;-). 3) In the same vein we should also continue to break down the boundaries between the application and its UI platform. note that this activity is orthogonal to the two above since existing 3.x parts will continue to be SWT-based for some time yet. Looking forward to having some time to get to the 'fun stuff', Eric From: Paul Webster <[email protected]> To: E4 Project developer mailing list <[email protected]> Date: 06/04/2012 11:57 AM Subject: Re: [e4-dev] Eclipse 4.2 Application platform based Products Sent by: [email protected] Hi Kai, The plan in 4.3 includes refactoring some of the workbench services into a more modular state, so they can be used with Eclipse4 applications PW -- Paul Webster Hi floor. Make me a sammich! - GIR _______________________________________________ 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
