Summary: | [Model] Umbrella bug to track and improve E4 model fragment handling | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Rolf Theunissen <rolf.theunissen> |
Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | laeubi |
Version: | 4.15 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.eclipse.org/bugs/show_bug.cgi?id=437958 https://bugs.eclipse.org/bugs/show_bug.cgi?id=509644 |
||
Whiteboard: | |||
Bug Depends on: | 379216, 440030, 469595, 526256, 529924, 547839, 551634, 551851, 562472, 571438, 369976, 381916, 478319, 571866, 572946 | ||
Bug Blocks: |
Description
Rolf Theunissen
2020-04-26 13:15:46 EDT
May I add another issue? Currently there is only a strategy for merging at startup but no strategy for removal or update. This currently leads to strange behavior (e.g. when a bundle is updated the fragment stays in place and now maybe outdated or invalid classes/objects are referenced. I'm not familiar enough to judge if its possible but maybe someone else could give an idea if this is possible: Its would be good if the model is not actually merged into one big "thing" but a dynamic structure is used that combines elements on the fly, then some of the problems would automatically disappear (e.g. ordering would only be an intermediate problem). Simple example: Instead of adding all elements to a global list, the global list is just a view that delegates to all child fragments (think about it as a UNION SELECT in SQL). |