483050 – Variables, properties and tags on supplementary tab in application model editor

Bug 483050 - Variables, properties and tags on supplementary tab in application model editor

Summary: Variables, properties and tags on supplementary tab in application model editor

Status:	NEW

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	IDE (show other bugs)
Version:	4.6
Hardware:	PC Windows NT

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assignee:	Jonas Helming
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-11-25 16:17 EST by Dirk Fauth
Modified:	2017-11-19 06:06 EST (History)
CC List:	5 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 Dirk Fauth

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

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

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

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

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.