A strawman page listing opportunities for better componentization in e4.
Note that E4/RCP Future is related to this.
The following are examples of code that should live in separate plug-ins so that they can be optionally left out when building applications based on the e4 Workbench.
- Editor management. Code that deals with editor inputs, content types, mapping between content types and editors, code that manages the open/save/close editor lifecycle, etc.
- Extensibility. We have quite some code that manages UI contributions from plug-ins, piecing it all together to form the final concrete UI. Applications that are not extensible in this way (i.e. applications that manage all UI contributions themselves) should not have to include this code.