[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [eclipse-incubator-e4-dev] Skeletal "IDE" app in the repository
- From: "Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>
- Date: Fri, 5 Sep 2008 08:20:44 -0700
- Delivered-to: email@example.com
- Thread-index: AckPZ+B8/YJBIXHrTpCo9q5jAjkuPQAAu+HA
- Thread-topic: [eclipse-incubator-e4-dev] Skeletal "IDE" app in the repository
Thanks, Kim. This is definitely something the resources team will be
interested in. I'm not sure of our timing but as we get going we'll need
to fix some of this stuff anyway.
> -----Original Message-----
> From: eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx
> [mailto:eclipse-incubator-e4-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Kimberly Horne
> Sent: Friday, September 05, 2008 10:58 AM
> To: E4 developer list
> Subject: [eclipse-incubator-e4-dev] Skeletal "IDE" app in the
> A new project, org.eclipse.e4.ui.ide.application, has been
> checked into the repository. This project (along with it's
> associated launch config, located in the demos project) will
> provide a skeletal "IDE"
> application. Right now, this consists of a navigator (that
> borrows from the photo app) as well as a text "editor" (that
> doesn't support saving). This editor is a view at the moment
> that's driven by selection in the navigator. If anyone would
> like to help flesh this out, please step forward. Some
> things we need to think about initially, off the top of my head:
> 1) rendering handler contributions under parts
> 2) creating a proper "editor" mechanism that isn't driven by
> selection and can have multiple instances
> 3) communicating state from parent parts to sub
> parts/handlers. This may be a way to inject services into
> your service locator, this may be something else.
> Specifically, how do we wire up "save"?
> 4) add other IDE like views. what do properties/outlines/etc
> look like in e4? what services/mechanisms do they require?
> eclipse-incubator-e4-dev mailing list