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 "ETrice/Development/Implementation ideas"
< ETrice | Development
(New page: = Implementation Ideas and Details = == Xtext == * Xtext grammar considerations == Graphiti == For the implementation of state machine animation we nee...) |
(→read-only mode of the editor) |
||
| Line 17: | Line 17: | ||
It checks whether the ToolBehaviorProvider is an instance of IFeatureCheckerHolder and if so retrieves its FeatureChecker. | It checks whether the ToolBehaviorProvider is an instance of IFeatureCheckerHolder and if so retrieves its FeatureChecker. | ||
For this the FeatureCheckerAdapter can be used. | For this the FeatureCheckerAdapter can be used. | ||
| + | |||
| + | === multiple instances of one diagram === | ||
| + | |||
| + | Derive from FileEditorInput and let this class hold the instance path. | ||
| + | Derive from DiagramEditorMatchingStrategy and extend the matching strategy. | ||
Revision as of 08:11, 16 August 2012
Contents
Implementation Ideas and Details
Xtext
Graphiti
For the implementation of state machine animation we need
- multiple instances of one diagram (several editors for one file)
- highlighting of states and transitions
- read-only mode of the editor
read-only mode of the editor
The read-only mode of the editor can be achieved by using the ConfigurableFeatureProviderWrapper. It checks whether the ToolBehaviorProvider is an instance of IFeatureCheckerHolder and if so retrieves its FeatureChecker. For this the FeatureCheckerAdapter can be used.
multiple instances of one diagram
Derive from FileEditorInput and let this class hold the instance path. Derive from DiagramEditorMatchingStrategy and extend the matching strategy.