Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Eclipse4/RCP"
(→Workbench Renderers) |
m (→Workbench Model) |
||
Line 37: | Line 37: | ||
*Customizing the Behaviour | *Customizing the Behaviour | ||
**Drag and Drop | **Drag and Drop | ||
− | *Extending the Model | + | *[[Eclipse4/RCP/Modeled UI/Extending the Model|Extending the Model]] |
− | **Defining New Model Elements | + | **[[Eclipse4/RCP/Modeled UI/Extending the Model#Defining New Model Elements|Defining New Model Elements]] |
*[[Eclipse4/RCP/Modeled UI/Addons|Addons]] | *[[Eclipse4/RCP/Modeled UI/Addons|Addons]] | ||
*Localization | *Localization |
Revision as of 11:07, 20 October 2011
Contents
Introduction
Eclipse 4 is the next generation platform for building Eclipse-based tools and rich client desktop applications. This new release makes it easier for developers to develop and assemble applications and tools based on the Eclipse platform.
Eclipse 4 introduces the following:
- a model-based user interface and a new CSS-based declarative mechanism for application styling. These facilities make it easier to design and customize an application user interface. This also adds greater flexibility to UI layout, making it easier to make a user interface look different from an IDE.
- a new services-oriented programming model that makes it easier to use discreet application services of the Eclipse platform.
Programming Model
Compatibility Layer
Workbench Model
Source material: http://wiki.eclipse.org/E4/UI/Modeled_UI
- Modeled UI
- Contributing to the Model
- Model Fragments
- Creating Model Elements at Runtime
- Modifying the Model
- Listening to Model Changes
- Defining the Application Layout
- Creating an e4xmi File
- Creating the Model Instance Programmatically
- Customizing the Behaviour
- Drag and Drop
- Extending the Model
- Addons
- Localization
- Suggesting Behaviour with Tags
Model Elements
Workbench Renderers
With the Eclipse 4 Application Platform, the UI model has been separated from how the model is rendered. Eclipse 4 ships with a standard SWT renderer, defined in org.eclipse.e4.ui.workbench.renderer.swt.
Renderers are installed through the XXX extension point. See YYY for an example of how to add a renderer.
What is the difference between #visible and #toBeRendered?
#visible captures whether the rendered UI elements are in presentation or hidden from view. With the SWT renderer, when #visible = false, then the element's widgets are reparented to an invisible shell; the widget is still alive, but won't be seen.
#toBeRendered captures whether this UI element should be rendered; it serves as an instruction to the renderer as to whether the element should or should not be rendered. When set to true, the renderer should explicitly When set to false, all resources are removed and nulled.
Application Services
Source material: http://wiki.eclipse.org/E4/Eclipse_Application_Services
- The "Twenty Things"
- Obtaining Services
- Contributing Services
- OSGi Services
- Common Services
- Workbench Services
- List of All Provided Services
Frequently Asked Questions
We have assembled a set of FAQs for Eclipse 4 development and another set for more general questions.