Community
Participate
Working Groups
Those 2 types are not really meant for usage by customers. I think we should move them to an extra .ecore in the area they are used (most likely in the org.eclipse.ui.workbench-bundle)
Post release we should re-examine all the changes we've made in the last while to see what's there...
Tom, for now how about just moving them to their own package? I'm just trying to limit complexity, if we have have multiple ecore models then the upgrade story will get much more complicated won't it?
Which upgrade process you are talking about 4.0 to 4.1? I personally think that we are going to have 1 or 2 breaking changes in our model (the keybinding story is probably one of them). This change only affects internal code because 2 those types are only created at runtime and deleted before shutdown by the compat layer (it does not get part of deltas - Paul/Remy can correct me on this)
Looking on the RenderedToolbar/RenderedMenu can't we simply remove them. To make storeing arbitary runtime information I think we should add a transient-Map-attribute to ApplicationElement or UIElement. Eric/Paul/Remy thoughts on this?
(In reply to comment #3) > This change only affects > internal code because 2 those types are only created at runtime and deleted > before shutdown by the compat layer (it does not get part of deltas - Paul/Remy > can correct me on this) MRenderedToolBars of views do get persisted actually. (In reply to comment #4) > To make storeing arbitary runtime information I think we should add a > transient-Map-attribute to ApplicationElement or UIElement. This would just be a Map<Object, Object>?
[...] > > MRenderedToolBars of views do get persisted actually. > > (In reply to comment #4) > > To make storeing arbitary runtime information I think we should add a > > transient-Map-attribute to ApplicationElement or UIElement. > > This would just be a Map<Object, Object>? I'd prefer a Map<String,Object>
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This is a mass change to close all e4 bugs marked with "stalebug" whiteboard. If this bug is still valid, please reopen and remove the "stalebug" keyword.
