Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Sphinx/stories"

(Metamodel services)
(Metamodel services)
Line 53: Line 53:
 
|}
 
|}
  
 +
{{CTable|tableWidth=64%}}
 
| Plug-in || Extension Points
 
| Plug-in || Extension Points
 
|-
 
|-
Line 64: Line 65:
 
|}
 
|}
  
 +
{{CTable|tableWidth=64%}}
 
| Plug-in || Extension Points
 
| Plug-in || Extension Points
 
|-
 
|-

Revision as of 17:48, 5 May 2014

User Stories

Architecture Refactoring

Essential Sphinx classes

Metamodel services

The idea is to collect most of Sphinx extension points under one extension point, the Metamodel Services. This unique extension point will provide the glue to manage a new metamodel by Sphinx and will have the flexibility to be dispatched over many plug-ins depending on the architecture.

The tables below show the current extension points and their corresponding plug-in

Plug-in Extension Points
org.eclipse.sphinx.emf customCommands
editingDomainFactoryListeners
metaModelDescriptors
modelConverters
resourceHandlers
resourceLocators
resourceScopeProviders


Plug-in Extension Points
org.eclipse.sphinx.emf.workspace editingDomains
modelSaveLifecycleListeners
uriChangeDetectorDelegates
uriChangeListeners

The tables below show an overview of the expected extensions points and their corresponding plug-in

Plug-in Extension Points
org.eclipse.sphinx.emf editingDomains
modelSaveLifecycleListeners
uriChangeDetectorDelegates
uriChangeListeners


Plug-in Extension Points
org.eclipse.sphinx.emf.edit editingDomains
modelSaveLifecycleListeners
uriChangeDetectorDelegates
uriChangeListeners


Plug-in Extension Points
org.eclipse.sphinx.emf.workspace editingDomains
modelSaveLifecycleListeners
uriChangeDetectorDelegates
uriChangeListeners

Back to the top