Bug 386829 - GMF-Tooling bootstrapping -- visual editor for diagram definitions
Summary: GMF-Tooling bootstrapping -- visual editor for diagram definitions
Status: ASSIGNED
Alias: None
Product: GMF-Tooling (ARCHIVED)
Classification: Modeling
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1   Edit
Assignee: Michael Golubev CLA
QA Contact:
URL:
Whiteboard: Entry Barrier
Keywords: plan
Depends on: 386832 393140
Blocks: 386830
  Show dependency tree
 
Reported: 2012-08-08 08:33 EDT by Michael Golubev CLA
Modified: 2013-06-06 06:11 EDT (History)
0 users

See Also:
borlander: kepler+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Golubev CLA 2012-08-08 08:33:37 EDT
Defining the GMF Tooling input artifacts in the tree editor is not very usable. 
Allowing users to define the diagrams in the Wysiwig matter would be much useful. 

In particular it allows to hide from un-experienced user the details of the underlying models and improves the learning curve. 

There are already some known successful attempts to do such kind of bootstrapping, e.g see GMF Simple Map project (http://code.google.com/a/eclipselabs.org/p/gmf-simple-map-editor/wiki/QuickStartGuide).

It seems reasonable to expect those diagram to be itself generated from the GMF-T artifacts. In theory, combined with #386821 it would allow to switch the same definition model between graphiti-based and GMF-runtime based look and feel. 

However the latter consideration should NOT be considered as a requirement per se, at least for the Kepler timeframe.