Bug 317556 - [Palettes] Papyrus shall support a life cycle management for palettes
Summary: [Palettes] Papyrus shall support a life cycle management for palettes
Status: ASSIGNED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Remi Schnekenburger CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted, plan
Depends on:
Blocks:
 
Reported: 2010-06-22 05:30 EDT by Remi Schnekenburger CLA
Modified: 2017-08-03 05:19 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Remi Schnekenburger CLA 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 CLA 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.