Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EATOP/architecture"
(→Root features) |
(→Root features) |
||
Line 83: | Line 83: | ||
|- | |- | ||
|org.eclipse.eatop.examples | |org.eclipse.eatop.examples | ||
+ | |} | ||
+ | |||
+ | |||
+ | ===Component features=== | ||
+ | Component features enable adopters to select and include individual Sphinx components in their applications. They are essentially a one-to-one representation of the architecture detailed above. Their IDs always include the name of the principal required Eclipse component that they are based on or extend. If necessary, they also indicate the name of the Sphinx component that they represent. The table below lists the component features that Sphinx offers for each of its components. | ||
+ | |||
+ | {|cellpadding="5" cellspacing="0" border="1" | ||
+ | !Top-level service | ||
+ | !Sub services | ||
+ | !Feature | ||
+ | |- | ||
+ | |rowspan="4"|Navigator & Editor Sockets | ||
+ | |Common Navigator Sockets | ||
+ | |org.eclipse.sphinx.emf.navigators | ||
+ | |- | ||
+ | |Form Editor Sockets | ||
+ | |org.eclipse.sphinx.emf.editors.forms | ||
+ | |- | ||
+ | |Nebula Extensions for Form Editors | ||
+ | |org.eclipse.sphinx.emf.editors.forms.nebula | ||
+ | |- | ||
+ | |GMF Editor Sockets | ||
+ | |org.eclipse.sphinx.gmf.editors | ||
+ | |- | ||
+ | | Validation Runtime Extensions | ||
+ | | | ||
+ | |org.eclipse.sphinx.emf.validation | ||
+ | |- | ||
+ | |M2x IDE Integration | ||
+ | |Xtend/Xpand IDE Integration | ||
+ | |org.eclipse.sphinx.xtendxpand | ||
+ | |- | ||
+ | |Eclipse PDE Extensions | ||
+ | | | ||
+ | |org.eclipse.sphinx.pde | ||
+ | |- | ||
+ | |rowspan="2"|XML Persistence Mapping | ||
+ | |XML Persistence Mapping based EMF Serialization | ||
+ | |org.eclipse.sphinx.emf.serialization | ||
+ | |- | ||
+ | |XML Persistence Mapping & XSD Schema Generators | ||
+ | |org.eclipse.sphinx.emf.serialization.generators | ||
+ | |- | ||
+ | |rowspan="3"|Core | ||
+ | |Workspace Management | ||
+ | |rowspan="3"|org.eclipse.sphinx.core | ||
+ | |- | ||
+ | |EMF Runtime Extensions | ||
+ | |- | ||
+ | |Eclipse Platform Extensions | ||
|} | |} |
Revision as of 07:24, 9 April 2014
Architecture
The following picture depicts the EATOP architecture. It depends on Eclipse Sphinx components.
Root features
Root features are the primary deliverables of EATOP and can be used to consume all or predefined subsets of EATOP components or examples at once. They can be individually retrieved from the EATOP Update Site or obtained as individual archives from the EATOP Downloads. The following root features are provided:
Feature | Description | Included plugins | Included features |
---|---|---|---|
org.eclipse.eatop.base | Includes EATOP base runtime binaries (without source code and documentation) | org.eclipse.eatop.metamodels | |
org.eclipse.eatop.workspace | |||
org.eclipse.eatop.base.sdk | Base SDK including runtime, source code and documentation (but no examples) | org.eclipse.eatop.base | |
org.eclipse.eatop.base.source | |||
org.eclipse.eatop.eastadl2112.sdk | The EAST-ADL metamodel 2.1.12 implementation including source | org.eclipse.eatop.metamodel2112 | |
org.eclipse.eatop.metamodel2112.source | |||
org.eclipse.eatop | Includes EATOP runtime binaries (without source code and documentation). | org.eclipse.eatop.base | |
org.eclipse.eatop.metamodel2112 | |||
org.eclipse.eatop.sdk | Includes EATOP runtime, source code and documentation (but no examples). | org.eclipse.eatop.sdk | org.eclipse.eatop |
org.eclipse.eatop.source | |||
org.eclipse.eatop.examples | Includes EATOP examples (with source code). | org.eclipse.eatop.examples.actions | |
org.eclipse.eatop.examples.actions.source | |||
org.eclipse.eatop.examples.common.ui | |||
org.eclipse.eatop.examples.commons.ui.source | |||
org.eclipse.eatop.examples.editor | |||
org.eclipse.eatop.examples.editor.source | |||
org.eclipse.eatop.examples.explorer | |||
org.eclipse.eatop.examples.explorer.source | |||
org.eclipse.eatop.demonstrator | |||
org.eclipse.eatop.demonstrator | Includes the EATOP runtime and a collection of examples that demonstrate the features and capabilites of the underlying platform, i.e., EATOP. It is a standalone application that can be used to conveniently explorer EATOP, it does not require an existing Eclipse installation | org.eclipse.eatop | |
org.eclipse.eatop.examples |
Component features
Component features enable adopters to select and include individual Sphinx components in their applications. They are essentially a one-to-one representation of the architecture detailed above. Their IDs always include the name of the principal required Eclipse component that they are based on or extend. If necessary, they also indicate the name of the Sphinx component that they represent. The table below lists the component features that Sphinx offers for each of its components.
Top-level service | Sub services | Feature |
---|---|---|
Navigator & Editor Sockets | Common Navigator Sockets | org.eclipse.sphinx.emf.navigators |
Form Editor Sockets | org.eclipse.sphinx.emf.editors.forms | |
Nebula Extensions for Form Editors | org.eclipse.sphinx.emf.editors.forms.nebula | |
GMF Editor Sockets | org.eclipse.sphinx.gmf.editors | |
Validation Runtime Extensions | org.eclipse.sphinx.emf.validation | |
M2x IDE Integration | Xtend/Xpand IDE Integration | org.eclipse.sphinx.xtendxpand |
Eclipse PDE Extensions | org.eclipse.sphinx.pde | |
XML Persistence Mapping | XML Persistence Mapping based EMF Serialization | org.eclipse.sphinx.emf.serialization |
XML Persistence Mapping & XSD Schema Generators | org.eclipse.sphinx.emf.serialization.generators | |
Core | Workspace Management | org.eclipse.sphinx.core |
EMF Runtime Extensions | ||
Eclipse Platform Extensions |