Difference between revisions of "ETrice/Development/Implementation ideas"

From Eclipsepedia

Jump to: navigation, search
(New page: = Implementation Ideas and Details = == Xtext == * Xtext grammar considerations == Graphiti == For the implementation of state machine animation we nee...)
 
(multiple instances of one diagram)
 
(One intermediate revision by one user not shown)
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.
 +
 +
[[Category:eTrice]]

Latest revision as of 03:20, 16 April 2013

Contents

[edit] Implementation Ideas and Details

[edit] Xtext

[edit] 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

[edit] 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.

[edit] multiple instances of one diagram

Derive from FileEditorInput and let this class hold the instance path. Derive from DiagramEditorMatchingStrategy and extend the matching strategy.