Bug 483050

Summary: Variables, properties and tags on supplementary tab in application model editor
Product: [Eclipse Project] Platform Reporter: Dirk Fauth <dirk.fauth>
Component: IDEAssignee: Jonas Helming <jhelming>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: daniel.kruegler, jhelming, Lars.Vogel, olivier.prouvost, tom.schindl
Version: 4.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows NT   
Whiteboard:

Description Dirk Fauth CLA 2015-11-25 16:17:06 EST
Currently the editors for MContext application model elements have the properties on the first tab, while variables and tags are on the Supplementary tab.

Variables and properties are tight connected, so they should be editable on the same tab.

So to make the editor more concise, tags, variables and properties should be located together on the Supplementary tab.
Comment 1 Jonas Helming CLA 2016-03-04 08:09:39 EST
I have also noted that "persisted state" is sometimes on the first, sometimes on the second tab. I can fix this, but before, we should discuss the desired state. I think "binding context" should stay on the first tab. So AFAICS, we have max the following things for the supplementery tab depending on the type:

Accessibility phrase
Tags
Persisted State
Variables
Context Properties

That would also be my preferred order, what do you think?
Comment 2 Dirk Fauth CLA 2016-03-04 08:17:59 EST
Sounds good to me. IIRC that is what Tom and I discussed at EclipseCon. 

@Tom 
What do you think?
Comment 3 Jonas Helming CLA 2016-04-29 02:18:47 EDT
@Lars: Before I start on this now, do we consider changes in the e4 tools UI an API break?
Comment 4 Lars Vogel CLA 2016-04-29 02:51:21 EDT
(In reply to Jonas Helming from comment #3)
> @Lars: Before I start on this now, do we consider changes in the e4 tools UI
> an API break?

Depends on the MANIFEST.MF, everything this is not exported or marked as x-internal/ x-friends is internal. If we did it correct in the past, the e4 tools should not define any API.