Bug 552639 - [Tools] Application model editor should derive possible elements from the EMF Model
Summary: [Tools] Application model editor should derive possible elements from the EMF...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.13   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-03 01:58 EST by Christoph Laeubrich CLA
Modified: 2019-11-04 07:16 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Laeubrich CLA 2019-11-03 01:58:39 EST 
Currently, possible elements are hard-encoded, leading to the situation that in several places elements are missing (see bug 551749 and bug 496833 for example) but sometimes there are to much elements offered, for example if one creates a model fragment that extends a certain elements child-list all possible elements are offered, but in fact only a small subset is allowed here.

Another point is, that the EMF Model might be extended, then the Model-Editor must be enhanced in some way to account for this new elements.

So the goal of this enhancement should be to evaluate possible options and enhance the Model-Editor in a way so that the EMF-Model is the base for building the editor.

Maybe EMF offers some kind of support already, if not it might be good to discuss with the EMF-project if a generic editor for EMF-Model-Object would be a good thing to place inside EMF and let the Application model editor base on this.
Comment 1 Christoph Keimel CLA 2019-11-04 07:16:10 EST 
+1 this would be a great feature