Community
Participate
Working Groups
- GEF allows for palette customization from the UI. - Need to integrate this capability and persist it in the workspace.
Additional comments: Partners need the ability to change the diagram editor toolbox to only have the items that their customers need. To accomplish this, they will need to: 1. Remove toolbox items from existing tabs 2. Remove existing tabs 3. Add their own tabs 4. Add their own items to existing tabs or newly created tabs This extensibility functionality will also be essential to OEM situations. The persisted workspace settings may need to be sharable or configurable through API...
*** Bug 114217 has been marked as a duplicate of this bug. ***
IMHO would be nice to have it sooooooooooner
Reassigning to Cherie who has related paletted work in M6.
Steve, what do you mean by Comment #1? Does this mean that they need to be able to do it before deploy time or just that items can be removed from the palette when the application is run like in the GEF logic example?
The expectation is that the workspace would be customized at runtime. Then teams could export and share their workspace to other team members if they wished to reuse the customization. I did some investigation of this and it looks like to persist the settings we merely need to implement the PaletteCustomizer interface and set it into the PaletteViewer customer. Here's some code from the EDiagramEditor: protected PaletteViewerProvider createPaletteViewerProvider() { return new PaletteViewerProvider(getEditDomain()) { protected void configurePaletteViewer(PaletteViewer viewer) { super.configurePaletteViewer(viewer); viewer.setCustomizer(new PaletteCustomizer() { public void revertToSaved() {} public void save() {} }); viewer.addDragSourceListener(new TemplateTransferDragSourceListener(viewer)); } }; }
Descoped officially from M6. May still be considered if time permits and if the fix as mentioned below is low barrier.
I have hooked up this capability in GMF. More specifically, - I have extended the PaletteCustomizerDialog to remove the toolbar items which we will not support in GMF. (We do not want to delete items as the user could never get them back and we have decided not to support reordering as it is questionable how this would be saved especially if capabilities are also adding/removing palette entries.) - I have added the concept of an IPaletteState which saves the state of a palette entry. This allows the PaletteCustomizer to revert the changes made in the Customize dialog if the user pressed Cancel (this did not work in GEF). - I am storing the customizations made in the workspace preferences. See the classes in the org.eclipse.gmf.runtime.gef.ui.palette.customize package for more details. Note: The saving of customizations does not currently work in GMF generated diagram editors because these editors do not have palette ids. This feature requires palette ids as this is how the palette entry is identified in the workspace preferences.
[target cleanup] 2.1 M4 was the original target milestone for this bug
From this bug description I guess you mean customizing palette by editor users, who can right click on palette and choose "Customize..." button, yes? Or is it possible to programatically customize palette for particular editor? thanks
(In reply to comment #10) > From this bug description I guess you mean customizing palette by editor users, > who can right click on palette and choose "Customize..." button, yes? > > Or is it possible to programatically customize palette for particular editor? > thanks > This enhancement implemented the GEF feature in GMF allowing customizing palette by editor users, not programatically.
[GMF Restructure] Bug 319140 : product GMF and component Runtime Diagram was the original product and component for this bug
