Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 207390

Summary: Certain GEF palette classes should be made public to make the palette more extensible
Product: [Tools] GEF Reporter: Anthony Hunter <ahunter.eclipse>
Component: GEF-Legacy GEF (MVC)Assignee: Anthony Hunter <ahunter.eclipse>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: ahunter.eclipse, bugbridg, hudsonr
Version: 3.3.1   
Target Milestone: 3.4.0 (Ganymede) M3   
Hardware: All   
OS: All   
Whiteboard:

Description Anthony Hunter CLA 2007-10-24 23:21:03 EDT 
There are two GEF classes that we will need to be public in order to properly support our palette extensions:

PaletteEditPart
PaletteToolbarLayout

The first class is required because if we add any new edit parts in the edit part hierarchy of the palette,, there is code that assumes that everything will be a PaletteEditPart. Also,, the PaletteToolbarLayout is required because we host drawer/group/tool/stack figures inside our palette tab figures. The base GMF/GEF figures expect the PaletteToolbarLayout to be in effect in their parent figure.
Comment 1 Randy Hudson CLA 2007-10-25 10:48:27 EDT 
Anthony, could you update the target milestone and link to the palette extensions you mention in the description? Making the palette implementation API will handcuff us when making future changes to the UI, which I thought was a planned item for 3.4.

I think it is valid for the palette to be internal. Similar UIs in the Workbench/JFace, like PerspectiveBarContributionItem, PartSashContainer, ViewStack, etc., are all internal to ensure freedom in future releases.
Comment 2 Anthony Hunter CLA 2007-10-25 11:51:01 EDT 
Completed with Bug 206800 .
Comment 3 Anthony Hunter CLA 2007-10-30 16:15:47 EDT 
Completed with Bug 206800 .