[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipse-incubator-e4-dev] 3.X API and e4
|
PS
also, how is that related to "Modeling the Workbench"
http://wiki.eclipse.org/E4/Modeling
My understanding was that Tom already has a prorotype
of a Modeled Workbench, wouldn't that be related such
that an annotation on each API concept could be "modeled"?
How does "will no doubt become deprecated or broken
in some capacity" relate to McQ's backward
compatibility requirement?
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: Oberhuber, Martin
> Sent: Tuesday, May 27, 2008 11:30 PM
> To: 'E4 developer list'
> 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: eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx
> > [mailto:eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx] 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
> > eclipse-incubator-e4-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
> >
