Skip to main content
AgeCommit message (Collapse)AuthorFilesLines
2020-06-05Bug 562935 - Migration to GMF Notation 1.13.0Florian NOYRIT1-3/+3
Migrate dependencies to org.eclipse.gmf.runtime.notation to [1.10.0,2.0.0) Migrate dependencies to org.eclipse.gmf.runtime.notation.edit to [1.8.0,2.0.0) Changed all occurences of to Updated the copy of the notation metamodel in to the new 1.10.0 metamodel Fixed some building issues in tests Change-Id: I9bb53de2558b67076f6fa423da522bdcedeb794b Signed-off-by: Florian NOYRIT <>
2016-02-12Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus7-121/+121 Factor UI dependencies out of the UML Element Types bundle. This includes moving some advices that interact with the user into a new org.eclipse.papyrus.uml.service.types.ui bundle. Pull up the PasteCommandService and IPasteCommandProvider API into the Infra Diagram layer where the extension point is defined. Deprecate the old API in the UML layer. Introduce a service for participation of languages in CSS styling: * styling reset actions in the Reset Style command * access to semantic model classes and properties to make available to CSS Factor PapyrusObservableValue and cohorts out of the UML Tools bundle into the Infra Layer for more general reuse and to relieve the Diagram Infrastructure layer of UML dependencies. The old API remains as deprecated. Remove the Infra Diagram Layer dependency on UML Layer for property testers governing deletion in the diagram. Includes introduction of a new IGraphicalDeletionHelper OSGi service for delegation of the determination of whether an element can be deleted from the diagram and replacement of the XML expression properties * org.eclipse.papyrus.uml.diagram.common.isSemanticDeletion * org.eclipse.papyrus.uml.diagram.common.isReadOnly by * org.eclipse.papyrus.infra.gmfdiag.common.isSemanticDeletion * org.eclipse.papyrus.infra.gmfdiag.common.canDelete (where the latter is the negation of the property that it supersedes) Extract UML dependencies from the Diagram Outline and CSS Editor bundles. Remove unused MDTUtil APIs that referenced a UML-specific annotation. Move the Diagram Infrastructure CSS Palette bundle into the UML layer because it serves to provide extensions on the Palette Service, which is an overtly UML-specific capability. All client APIs for the Properties View are moved from bundle to a new bundle. This includes renaming of: * extension points * label-provider contexts * XWT namespaces Add an "all UI tests" suite. Define a componentized hierarchical build layout of the main plug-ins Change-Id: I43f8f3644857a18b69715f5a2f1da9b1cf286d67
2015-11-26Bug 482927: [Properties] Customization context models should have UI labelsChristian W. Damus1-106/+106 Add an optional 'label' attribute to the Context class and a derived 'userLabel' that is the 'label' if present, otherwise the 'name'. Use the new derived user label wherever appropriate in the UI: in progress monitors, informational dialogs, and especially the preference pages. In the "Property view" preference page, sort contexts by user label. Update existing context models to provide user-friendly labels.
2015-11-13[CSS - Properties] Change label of CSS Classes for consistencyCamille Letavernier1-106/+106
Change-Id: I550c86eb0165ac25028bf788f11b8843a97316ee Signed-off-by: Camille Letavernier <>
2014-04-30430079: [CSS] Papyrus shall provide features to define local themeCamille Letavernier1-2/+4 - Minor fix on file extensions for images
2014-04-30430079: [CSS] Papyrus shall provide features to define local themeGabriel Pascual2-88/+138 Patch 3 : - Fix major issue - Fix comment's remarks Patch 2 : - Rebase to pass hudson verification Pathch 1 : - Use workspace relative path for selected css files during CSS theme edition - Fix "restore default" button action in CSS preference page - Harmonisation of all UI for theme icon selection - Add dialog to confirm theme deletion - Refactor to resolve some dependency problems - Creation of widget for XWT theme view - Add embedded style sheets in CSS Workspace engine working - Fix problems of label provider for CSS themes properties view - Add workspace themes preference page - Add definition of theme property view - Fix saving step of an edited theme from workspace - Fix loading of theme icon in label provider - Fix behavior of theme edition dialog fields - Add edition action on style sheets list - Add move up and move down actions in edition dialog - Add actions (add and delete) to dialog - Resolution staying conflicts after last merge - Add edition theme dialog from project explorer - Minor modification of Style sheet metamodel - Modify CSS engine and theme manager to look at workspace theme contributions - Add theme creation by selecting one or more CSS files - Add dialog to define theme from CSS file in workspace - Create one menu for two actions to manage local theme - Manage command ID in handler - Fix containment relationship in model - Add draft of theme creation from a CSS selection - Modification of style sheets model - Add popup menu on CSS file Change-Id: Ie46281e334252bfbed727c18a431677761db2a45 Signed-off-by: Gabriel Pascual <>
2014-04-29429642: [Model / CSS] Add properties view to define Model's stylesheetsMickael ADAM2-7/+17 -Adding Forgotten dependency in a manifest Previous changes: -Change CSSStyleSheetProvider to return styleSheet contained on modelStyleSheet -if doesn't exists, add modelStyleSheet on a transaction without command Previous changes: -Add transactionnal command to add modelStyleSheet if dosent exists -Change resourceListener to adapter attached to modelStyleSheet and StyleSheet Previous changes: -Replace Ressource by Resource -Remove Notation import package on manifest -Use DestroyElementRequest + ServiceEdit on remove commands -Delete ModelStyleSheetContentProvider -> We don't use it but the CSSStyleSheetContentProvider instead which does the same things. -Add condition on modelCSSEngine's listener -Some JAutodoc formating -Fix "When we add the first model stylesheet on a Model, the ModelStyleSheets widget doesn't display it" The first commit's message is: -Add a ModelStyleSheet Observer List for the style properties view -Modify ModelCSSEngine to refresh model at ressource changes Change-Id: Ibb247e102c8360933036c5f1eea8382858eb021d Signed-off-by: Mickael ADAM <>
2014-02-25323802: [General] Papyrus shall provide a read only modeChristian W. Damus3-3/+3 Make presentation of the Reset Style button in the Appearance properties sensitive to the read-only state of the notation view. This requires injecting the CSS property into the widget from the XWT model so that the input may be consulted for editability.
2013-12-04370797: [Theme] Papyrus should provide a support for CSS files on itsCamille Letavernier3-3/+3
diagrams Fix the reset style handler
2013-04-23399869: [Widgets] Papyrus shall implement extension filters on the ↵cletavernie1-1/+15
“import…” UI
2012-04-02370797: [Theme] Papyrus should provide a support for CSS files on its diagramscletavernie6-0/+187

    Back to the top