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

Bug 317556

Summary:	[Palettes] Papyrus shall support a life cycle management for palettes
Product:	[Modeling] Papyrus	Reporter:	Remi Schnekenburger <rschnekenburger>
Component:	Core	Assignee:	Remi Schnekenburger <rschnekenburger>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	papyrus-bugs
Version:	0.8.0	Keywords:	helpwanted, plan
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Remi Schnekenburger

2010-06-22 05:30:48 EDT

It should be possible to manage the life cycle of palettes in Papyrus. 
It should be for example possible to define a right management on palettes (admin, user, etc), some palettes which should be not removable and/or modifiable. 
It should be also possible to replace a palette with another one. 
We will welcome all input from Papyrus users and developers, in order to improve the usability and the user experience with the palette.

Comment 1 Yann Tanguy

2010-06-28 04:46:32 EDT

The "customization features" shall be separated from modeling features.
In other words if the customization feature is not installed, the user should only get access to a predefined tool customization but may not customize the tool himself (feature not available).

As a side effect of being able to retrieve images in plugins, the Palette customization feature adds dependencies to some plugins (org.eclipse.jdt, org.eclipse.team,...) which are not directly necessary when using Papyrus for modelling.