Martin, at this point I think the answer is "We'll see". We can loosely break the API into a few types of methods:
Querys: All the 'get<xxx>' and 'is<yyy>' - at the end of the day we should be able to answer these directly from some part of the WB Model (and thanks Kim, having this available is going to help drive the model's definition...;-) Operations: methods that actually cause things to happen - The model-based version would have the functionality backing these methods implemented as Commands/Handlers that the API legacy support would invoke. Hooks: All the Listener type API; including the RCP's Advisors; anything that requires 'callback' handling...The handling for these is less straightforward. For any particular listener 'pool' (I.e. perspective listeners) we can presumably create a WB model listener that listens for the equivalent change in the new WB model and forwards the corresponding legacy event to its listeners. I'm expecting that we'll get at least a few ordering issues however, places where the event order in the new world may not match that of the legacy WB. For these I think that rather than complicate the new code we should tackle these as they arise. Onwards, Eric "Oberhuber, Martin" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 05/27/2008 05:29 PM Please respond to E4 developer list <[email protected]> To "E4 developer list" <[email protected]> cc Subject RE: [eclipse-incubator-e4-dev] 3.X API and e4 Thanks Kim, I'm just wondering how that is related to the work on http://wiki.eclipse.org/E4/Eclipse_Application_Model My understanding was that the goal of this also was to come up with a bird's eye view of the Services and their API's, also in order to harmonize them? Cheers, -- Martin Oberhuber, Senior Member of Technical Staff, Wind River Target Management Project Lead, DSDP PMC Member http://www.eclipse.org/dsdp/tm > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Kimberly Horne > Sent: Tuesday, May 27, 2008 6:35 PM > To: E4 developer list > Subject: [eclipse-incubator-e4-dev] 3.X API and e4 > > As we begin to implement e4 in ernest (we're doing that soon, > right? > right? :) it would be helpful to have an understanding of > what APIs we > currently expose in 3.X and what their applicability in the > brave new > e4 world might be. With that in mind, I've created > http://wiki.eclipse.org/E4/3X_API_Survey > to serve as a birds eye view of our existing API. As we > work on e4, > some of these will no doubt become deprecated or broken in some > capacity and having a page that expresses their condition would be > helpful. The eventual output of such a page is the porting guide. > > I've only enumerated the org.eclipse.ui (and ui.workbench) > plugins and > even then they're only really a skeleton - the observations > I've made, > while being consistent with the outcome of the summit, are > only there > as a placeholder. Additional input from interested parties would be > welcome. Having sections for PDE, Equinox, runtime, resources, and > whatever other plug-ins we're dragging into the e4 would be good as > well. > _______________________________________________ > eclipse-incubator-e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev > _______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
_______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
