


It is almost impossible to ship a ready-to-use distribution of Papyrus with a custom theme. It is not easy to export a Theme, as they are stored in the Eclipse preferences.If we wanted to change the current theme, we'd have either to change each object's appearance one by one, or to write an automatic transformation, which could be really complicated.We'd have to create "Blue classes" and change some of them to "Green"manually. It is not possible to create different categories of appearance for the same semantic Element (e.g.While this allows defining a custom theme for our diagrams, this mechanism suffers from a few limitations: Preferences page: change the initial appearance of all newly created element(s).Appearance tab (Properties view): change the appearance of the selected element(s).Until now, in Papyrus, this customization could be done by two complement means: Nevertheless, for a better readability (and even esthetic), the user has a certain freedom for changing some graphical properties, such as an Element's color. A Class is a rectangle, with optional compartments for its attributes and operations, and its name should be displayed in italic if the Class is abstract). However, it only focuses on the general representation of these elements (e.g. The standard UML specification provides a few hints to represent graphical elements.
