Summary: | Variables, properties and tags on supplementary tab in application model editor | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Dirk Fauth <dirk.fauth> |
Component: | IDE | Assignee: | 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
2015-11-25 16:17:06 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? Sounds good to me. IIRC that is what Tom and I discussed at EclipseCon. @Tom What do you think? @Lars: Before I start on this now, do we consider changes in the e4 tools UI an API break? (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. |