Planning page for Luna
Draft to develop a plan for our work in Luna
The general themes that we should focus on in Luna.
Exposing Eclipse4 in the Workbench
The Workbench (a.k.a compatibility layer) manipulates the model to host 3.x views and editors on it. In Luna we'd like to see Eclipse4 parts and other contributions contributed to the Workbench and provide 3.x wrappers to correctly interact with them in the Workbench.
Fragments and Extension Points
The fragment processing needs some more design work. The goal is to simplify the creation of fragments and to apply them in a standard way that is predictable.
Some enhancements in that area:
- bug 324954 - [Model] Allow model fragments to use XPath-Syntax to decide where to contribute
- bug 396974 - Multiple Parents for MenuContribution item
It would be nice if there was a tool where you could create your structure, select elements, and generate a fragment.
Graduate Relevant Eclipse4 tools
There are tools still in the E4 incubator that we should look at graduating or moth balling in Luna. Some currently under consideration:
The Lightweight CSS editor will probably need some work before it can graduate, as it would bring in the XText runtime. See bug 410841 - Explorer editing CSS with orion
Eclipse Application Services
See E4/Eclipse Application Services as a starting point, although our understanding has changed some of the categories.
Logging and Tracing
We need to decide on our logging and tracing strategies, and which APIs to use (ex, just use Equinox Logging and DebugTrace?). Then we need to apply that strategy to many of our new Eclipse4 plugins.
There was some discussion about using equinox concurrent support, and re-framing our scheduling/progress in terms of that. We need to analyze the difference between Jobs and IWorkbenchRunnableWithProgress and the concurrent support, and then look at our Eclipse4 level support. i.e. Do we use Jobs + provide Progress? Does Jobs need to be in terms of equinox concurrent? Do we need a parallel progress pattern with equinox concurrent?
We need to provide the fully functioning Eclipse4 save lifecycle, that the Workbench save lifecycle can be implemented on top of.
Workbench Services Decoupling
It's always been our goal to break up many of the Workbench services so they can be consumed by Eclipse4 applications without consuming the entire Workbench. Some examples:
- ISharedImages service
- Progress view service
- Error log service
- Preference management
- Properties management
- New wizards
Our starting priority here was the Error log and Progress view.