Skip to main content
aboutsummaryrefslogtreecommitdiffstats
path: root/plugins/infra/gmfdiag/css/org.eclipse.papyrus.infra.gmfdiag.css.properties
AgeCommit message (Collapse)AuthorFilesLines
2018-08-21Bug 537653 - [EPL] Update java files headersQuentin Le Menez36-72/+144
- replaced the reference in the java files headers - added the SPDX-License-Identifier Change-Id: Ia376515730e2430e8671c2b5c66f7b510894e5c6 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2018-07-04Bug 535808: [DevTools] Apply Cleanup & Format on saveCamille Letavernier2-0/+65
https://bugs.eclipse.org/bugs/show_bug.cgi?id=535808 - Propagate the new preferences to all projects Change-Id: I0e70c1c4a5d14a24c2d92371c27dad085e9aa2d3 Signed-off-by: Camille Letavernier <cletavernier@eclipsesource.com>
2018-05-28Bug 535185 - Add Automatic-Module-Name header for Java 9 compatibilityBenoit Maggi1-0/+1
- add Automatic-Module-Name with the same value as Bundle-SymbolicName in all Manifest.MF - quality fix : remove unused import Change-Id: Icd3e4376bc9e61e360ac61522b967a088a248480 Signed-off-by: Benoit Maggi <benoit.maggi@cea.fr>
2018-01-18Bug 528421: [API Tools] Change default settings for Papyrus projectsCamille Letavernier1-6/+12
https://bugs.eclipse.org/bugs/show_bug.cgi?id=528421 - Use more flexible options wrt. Constant values and Reexported APIs - Display errors directly in the code rather than Manifest, when relevant Change-Id: I7a48bca8a9a84487957a3d97a8dddfb145cdfd78 Signed-off-by: Camille Letavernier <cletavernier@eclipsesource.com>
2018-01-09Bug 515367 - [releng] Uniformization of the end of lines to Unix standardQuentin Le Menez21-1736/+1736
- Format the EOL of all the files matched by: grep -rIUs . | xargs -Ifile dos2unix -k 'file' Change-Id: I5c41d540a9a67b50de9b912ab35e16cc9a912961 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2017-12-22Bug 528992 - [CSS] There should be a way to remove a styleQuentin Le Menez1-0/+74
- Add a new remove style command Change-Id: I10086c959aee83239bd5198499a060663b6ae269 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr> (cherry picked from commit 4da7dfa2a6d3d35a1e4f52289b669c710d300ebd)
2017-11-20Bug 518305 - Apply a predefined Style directly from a diagramBenoit Maggi1-0/+72
- add apply style menu on right click - also works with multi-selection Change-Id: I445331e15aaf9a1bbdb1f2d229297b75bce8197f Signed-off-by: Benoit Maggi <benoit.maggi@cea.fr>
2017-09-01Bug 521572 - [General] Various cleanupsPierre GAUTIER2-0/+4
https://bugs.eclipse.org/bugs/show_bug.cgi?id=521572 define project-specific, overriding workspace-scoped, preferences for UTF8 encoding and Unix end of line preferences Change-Id: I260d84ab76c08866cd3e8709967d4218d992c095 Signed-off-by: Pierre GAUTIER <pierre.gautier@cea.fr>
2017-08-29Bug 520271 - [Property View] Generator should ignore redefined properties.Vincent Lorenzo2-5/+6
Change-Id: I5d73f2441ff5e23f937ab155488cf29fb249a65c Signed-off-by: Vincent Lorenzo <vincent.lorenzo@cea.fr>
2017-04-06Bug 514332 - Papyrus should never reexport non-singleton pluginsBenoit Maggi1-17/+19
- remove Required-Bundle Guava (and their re-export) - use package import for Guava dependencies Change-Id: Ie1e383b6b8ed1d57747345c2788c0c63de1f08bb Signed-off-by: Benoit Maggi <benoit.maggi@cea.fr> Signed-off-by: Florian Noyrit <florian.noyrit@cea.fr>
2017-03-30[releng] Update plugins and feature version numbers for Oxygen withFlorian Noyrit1-17/+17
Neon.3 as baseline Change-Id: Icb3b699de6846ce60370a1fedc169e1df741ace2
2016-08-28Bug 443799 - Fix potential bugs identified by FindBugs in oep.infra.*Florian Noyrit3-16/+16
Bug 499554 - Oxygen release version number moved to 3.0.0. Change-Id: I8e112db7175a5b89eb9b37973639627a6c29e007
2016-08-04Bug 492891: [Table] Link with editor: different behavior of diagrams andNicolas FAUVERGUE1-1/+1
tables https://bugs.eclipse.org/bugs/show_bug.cgi?id=492891 - The owner of table can be modified and the context can't be modified - Add the 'Table', 'Appearance' and 'Paste' tab in properties view when an the table is the current editor This looks to correct other bugs: - Bug 492605 - [Table][Properties][usability] error message "Properties are not available" - Bug 492615 - [Table][usability] inconsistency of properties view N.B: The 'invert axis' button doesn't work correctly, but another gerrit manage it Change-Id: I9d22713e81bf865bc59fbd10a34b270e75aa5037 Signed-off-by: Nicolas FAUVERGUE <nicolas.fauvergue@all4tec.net>
2016-03-03Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus3-1/+105
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Complete the configuration of PDE API Tooling in the Papyrus Main and Developer Tools projects, including: * adding the API Analysis nature and builder to .project where it was missing * adding a new menu action in the dev tools Project Management menu to ensure that all Oomph version-management projects in the workspace have API analysis also * fixing API version analysis problems, mostly by upversioning bundles to 2.0 but also applying API filters in some cases where it seems appropriate * implementing project-level API Analysis preferences for warning severity of missing @since doc tags (the default is error) and adding it to the Oomph project preferences management Change-Id: I3f5fad20ffc7bb66eec0abbb86b5cc52aacb1ff1
2016-02-24Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus2-55/+51
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Implement version management: PDE API Tooling and Oomph Version Management. Introduce two new plug-in projects to manage versioning using Oomph: * org.eclipse.papyrus.releng.main.release for the Main bundles and features * org.eclipse.papyrus.releng.dev.release for the Dev Tools Add new menu actions to the Dev Tools: * main menu bar: * synchronize POM and manifest versions * "Configure" context menu on bundle projects and MANIFEST.MF * optimize bundle dependencies and re-exports * update dependency version ranges to match current workspace and PDE target Remove obsolete menu actions from the Dev Tools: * main menu bar: * Set all Papyrus feature versions * Set all Papyrus plug-in versions * Set versions of all Papyrus dependencies in Papyrus plug-ins Fix versioning errors reported by PDE and Oomph. Ensure proper version ranges consistent with latest build target. Optimize the dependencies of all Papyrus Main bundles and Dev Tools. Remove version- and reexport-checking tests in the BundlesTests that are now not needed because, on the one hand, we now implement discrete bundle versioning (managed by PDE/Oomph) and on the other, we now use re-exports properly to ensure classpath consistency in clients of a bundle's API. Thorough overhaul of the "project editors" API, including: * rationalize the API interfaces * refactor the all-in-one PluginEditor class from the customization bundle to the project-editors bundle * update clients in the Customization and DSML Validation components * fix a bunch of operations that didn't work * add missing operations required by the new Dev Tools actions * complete some unimplemented APIs * add a comprehensive JUnit test suite covering all of the project-editors API Change-Id: I6a699d93909f61099226ceb994140f03ea99a70f
2016-02-13Revert "Bug 485220: [Architecture] Provide a more modular architecture ↵Christian W. Damus1-1/+0
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220" This reverts commit f050d4119a2316b27588076d4fc90152773fc019.
2016-02-13Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus1-0/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Fix build failure to resolve bundles in referenced p2 repositories by restoring the missing <groupId> elements in the POMs which, as it turns out, are not inherited from the parent module, despite what the m2e validator says. Change-Id: I62dacc9c70c940d28c3c02e1e35c8f874a7d3df0
2016-02-12Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus19-409/+406
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 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 org.eclipse.papyrus.views.properties bundle to a new org.eclipse.papyrus.infra.properties.ui 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
2016-01-22Bug 485220: [Architecture] Provide a more modular architecture (& builds) ↵Christian W. Damus7-8/+8
for Papyrus https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Refactor the Properties Model bundles into the Infra Layer. The *.views.properties.model[.edit,.editor] bundles are renamed as *.infra.properties[.edit,.editor]. The packages within are correspondingly renamed. To support upgrade installation, special p2 update metadata tells the p2 engine how these bundles have been renamed, ensuring proper replacement of the old *.views.properties.model* bundles, because otherwise the clash of EMF model registrations would cause run-time errors. The *.views.properties.environment extension point is moved to *.infra.properties.environments. The *.views.properties.context extension point has the <context> element moved to a new *.infra.properties.contexts point. The <preferencePageBinding> element remains. JUnit tests pass, at least inasmuch as they pass in the nightly builds. Change-Id: I6445808f8eb1144b08c0cd5f0a487d1bad229a4c
2016-01-22Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus8-13/+14
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Move UI-dependent APIs from the org.eclipse.papyrus.infra.emf bundle to a new org.eclipse.papyrus.infra.ui.emf bundle. Accordingly move tests into a new org.eclipse.papyrus.infra.ui.emf.tests bundle. Now that we have an UI EMF bundle, move the editor-page advices from the infra.ui bundle into it, which is a more appropriate home for them. One UI dependency is removed by reordering of code in the EMFHelper::getEObject(Object) API: * the EMF Facet tree elements are once again IAdaptables, providing their encapsulated EObjects or EReferences as adapters. So, the case handling IAdaptable is moved ahead of the test for is-an-EObject because these tree elements are also EObjects but are not interesting in themselves Also, the dialog-settings for the EMF Facet customization manager are moved into the infra.ui.emf bundle, as is the lazy initialization of the manager from those settings. Clients are refactored to get the customization manager from this new bundle (via a new ProviderHelper API) to ensure this lazy initialization. Various UI-dependent ServiceUtilsForXyz classes that were in the infra.emf bundle but had nothing to do with EMF are moved into the infra.ui bundle. UI-dependent classes from the org.eclipse.papyrus.infra.emf.readonly bundle are moved into the org.eclipse.papyrus.infra.ui.emf, also. These include extraction of the editor reload listener from the ReadOnlyManager class by means of a new general-purpose IReadOnlyManagerProcessor OSGi service interface. Tests all still pass (inasmuch as they do in the nightly master builds). Change-Id: Ieb0993b2ed1a7a49890d3471c7b42bc4f218fec6
2016-01-22Bug 485220: [Architecture] Provide a more modular architectureChristian W. Damus3-3/+4
https://bugs.eclipse.org/bugs/show_bug.cgi?id=485220 Move UI-dependent APIs from the org.eclipse.papyrus.infra.tools bundle to org.eclipse.papyrus.infra.ui. Accordingly move tests into a new org.eclipse.papyrus.infra.ui.tests bundle. Two crucial UI dependencies are inverted by introduction of new OSGi services with core interfaces specified in the non-UI layer: * IExecutorService extends Java Platform's ExecutorService with APIs for synchronous execution (a la Display.syncExec). A new CoreExecutors class in the infra.tools bundle supplies the instance provided by the OSGi service implementation in the infra.ui bundle. This provides compatibility for clients of various UIUtil APIs that they can no longer access * IContextualServiceRegistryTracker abstracts the concept of the default ServicesRegistry found in the currently active editor, which the ServiceUtilsForHandlers class (and hence all of its clients) relies on. Again an OSGi service implementation in the infra.ui bundle supplies the implementation of this tracker, which is exposed in infra.core through the service-utils API Also move UI-dependent APIs from the org.eclipse.papyrus.infra.core bundle into org.eclipse.papyrus.infra.ui. This includes * moving the 'papyrusDiagram' and 'papyrusContentOutline' extension points into the org.eclipse.papyrus.infra.ui namespace * moving various UI-related services such as EditorLifeycleManager, SaveLayoutBeforeClose, and the IMultiDiagramEditor, itself, into the org.eclipse.papyrus.infra.ui bundle This necessitates not only widespread refactorings on the moved APIs, but also concomitant move of other APIs in other bundles because they cannot plausibly use these moved APIs from their new home in org.eclipse.papyrus.infra.ui and/or they cannot reasonably also be moved to the UI bundle and/or they must be used by bundles that now have no UI dependency: * the DI/sash-windows EMF model is moved out of infra.core.sasheditor.di bundle into a new model-only org.eclipse.papyrus.infra.sashwindows.di bundle (which symbolic name incidentally now better reflects the contained Java package names) * the IPageManager and ILocalPageService interfaces are moved out of infra.core.sasheditor.di bundle because they need to remain accessible by headless code such as the edit advices that ensure deletion of sash-model pages for notations that are deleted. These are now in a package named org.eclipse.papyrus.infra.code.sashwindows.di.service. Accordingly the class hierarchy implementing the IPageManager interface is changed: the obsolete PageMngrImpl is deleted, replaced by a BasicPageManagerImpl which now the PageManagerImpl extends. A service factory creates the basic page manager in a headless context, but is overridden by the UI-aware implementation when the UI bundles are installed * the MultiDiagramEditorGefDelegate (which has a GEF 3 dependency) is moved from the org.eclipse.papyrus.infra.core.sasheditor bundle to a new org.eclipse.papyrus.infra.gmfdiag.gef bundle. Its usage for an adapter of ActionRegistry type is extracted out of the CoreMultiDiagramEditor class into a new external adapter-factory in the infra.gmfdiag.gef bundle Tests all still pass (inasmuch as they do in the nightly master builds). Change-Id: I573dee5d9312d6e5746d74575350d0152b591ab3
2015-11-26Bug 482927: [Properties] Customization context models should have UI labelsChristian W. Damus1-106/+106
https://bugs.eclipse.org/bugs/show_bug.cgi?id=482927 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 <camille.letavernier@cea.fr>
2015-08-24475724: NullPointerException inCamille Letavernier1-2/+15
CSSStyleSheetContentProvider$1.getElements (54) https://bugs.eclipse.org/bugs/show_bug.cgi?id=475724 Change-Id: If997742a062391bbd5266c16dc17bdbb4fd5bb54 Signed-off-by: Camille Letavernier <camille.letavernier@cea.fr>
2015-08-21[releng] Neon-1.2.0 modification step by stepQuentin Le Menez2-25/+22
Change-Id: I9126d707fecad85c9b5384b35074deba995b6527 Signed-off-by: Quentin Le Menez <quentin.lemenez@cea.fr>
2015-06-11469953: [Releng] Update the build to support a global POMCamille Letavernier1-2/+2
https://bugs.eclipse.org/bugs/show_bug.cgi?id=469953 Change-Id: I050cf9dbbdd5705aaf8d45f2db3458226d148002 Signed-off-by: Camille Letavernier <camille.letavernier@cea.fr>
2015-05-27468345: [CSS - Properties View] When creating a new ModelStyleSheet,Camille Letavernier1-0/+22
several commands are executed: need to undo several times https://bugs.eclipse.org/bugs/show_bug.cgi?id=468345 - Partial fix (See Bug 468345 / Comment 1) Change-Id: I64acb5dea67be212f2a56f910d65939da20b11fb Signed-off-by: Camille Letavernier <camille.letavernier@cea.fr>
2015-05-26467863: [CSS - Properties View] Read-only exception when trying toCamille Letavernier2-34/+76
silently create a ModelStyleSheet element https://bugs.eclipse.org/bugs/show_bug.cgi?id=467863 - Create the Stylesheet in the Notation resource only when we actually try to modify model stylesheets Change-Id: Ia83053016069b0745f41f511465315fef6f83ee1 Signed-off-by: Camille Letavernier <camille.letavernier@cea.fr>
2015-04-20Bug 433206: Papyrus shall enable local synchronization between graphical ↵Christian W. Damus1-1/+7
element and element in the model https://bugs.eclipse.org/bugs/show_bug.cgi?id=433206 Document the 'canonical' CSS property. Ensure a sensible drop command label, now that every drop operation always shows a menu.
2015-03-25Bug 433206: Papyrus shall enable local synchronization between graphical ↵Christian W. Damus1-3/+3
element and element in the model https://bugs.eclipse.org/bugs/show_bug.cgi?id=433206 (1) Refactor the 'uml.diagram.synchronizeview' plug-in: * remove the UML dependency (supplied by a UML-specific default children strategy) * move into infra.gmfdiag component * rename for GMF-standard 'canonical' terminology * API types, extension points, etc. renamed for 'canonical' terminology * fix parsing of priorities and other problems in the extension-point loading * support listening to multiple dependent model elements for canonical refresh * add a notion of default semantic children strategies for edit-parts that don't have specific requirements but can rely on a generic implementation (2) Implement a canonical request wrapper to pass through the drop request to default drop edit policy provided by the diagram, by-passing the pluggable strategies to which the CustomizableDopEditPolicy delegates. (3) Implement a toggle action in the various diagram filter menus to toggle canonical synchronization. (4) Enable the canonical edit policy provider. This requires additional changes: * only activate the canonical edit policy when the style is applied and is enabled because otherwise GMF assumes that canonical mode is on and treats connections as canonical (GMF run-time only checks that the edit policy is installed and is active) * listen for changes to the canonical style to disable/enable the canonical edit policy on the fly (5) Fix undo/redo of canonical view creation and of canonical enablement. (6) Properties view support for model/view synchronization (canonical edit policy). (7) Adapt SysML test utility to account for possible inclusion of ToggleCanonicalModeCommand by GMF in drop commands. (8) Implement deferred loading of synch child strategies and XML enablement expressions. (9) Fix problems in handling of connections incoming and outgoing canonical top shapes. (10) Support for a CSS 'canonical' style attribute. (11) Initial simple canonical synchronization scenarios for JUnit test cases. (12) Integrate canonical edit policy tests into the build. (13) Test cases for toggling canonical on/off, with undo/redo. Test cases for adding elements to the semantic model, with undo/redo. Test cases for deleting elements from the semantic model (including by simple remove, which unlike destroy does not also deletes dependent views anyways), with undo/redo. (14) Add regression tests for creation/deletion of elements and views together per the usual diagram editing scenarios, in the context of canonical diagrams. (15) Fix problems in canonical creation (with undo and redo) of connection views for non-owned relationship elements. (16) Add tests for CSS control of canonical synchronization. Fix inability to override CSS canonical style to turn synchronization off on selected views. Bug 461629: [CSS] Diagram refresh undo/redo problems https://bugs.eclipse.org/bugs/show_bug.cgi?id=461629 Implement new DiagramHelper refresh APIs to fix a few problems: - encapsulate synchronous (forced) and asynchronous refresh in new API methods. Deprecate the old methods that required clients to follow several steps. Update various client call sites to use the new API instead of the deprecated API - add corresponding APIs for refresh of individual DiagramEditParts, with similar heuristic for dropping redundant refresh requests - re-implement asynchronous refresh to use a new TransactionalEditingDomain executor that runs tasks as pre-commit trigger commands, to capture any undo/redo information for model changes - implement a new transaction option in the Papyrus editing domain that prevents runExclusive calls creating read-only transactions nested within a write transaction, so that canonical changes ensuing from edit-part refresh during refresh tasks can be properly recorded (without unprotected writes nested in the read-only context) Bug 433206: Papyrus shall enable local synchronization between graphical element and element in the model https://bugs.eclipse.org/bugs/show_bug.cgi?id=433206 (17) Enable test cases unblocked by the fix for undo/redo problems in diagram refresh (being bug 461629). (18) Do not record the edit-part but the view in the SetCanonicalCommand to support undo/redo even if the diagram has been closed and re-opened in the mean-time. To refresh the CanonicalEditPolicy's activation state after execute/undo/redo, the command now searches on the fly for all edit-parts (in all open diagram editors) that present the view in question. (19) Implement a new 'semi-active' state in the PapyrusCanonicalEditPolicy that is its minimally active state. This allows the edit policy to react to semantic model changes to delete views for deleted model elements, where such views are ones that it had originally created by canonical refresh. This relies on new tracking of canonically- created views, which in turn relies on a new utility for digging through complex command tree structures to get the views that were created by them. Includes automated tests for non-transactional refresh creating canonical views, with undo and redo in the semantic model undoing and redoing creationg of the elements that had been canonically created, after the canonical edit policy was (non-transactionally) disabled. (20) Don't forget about views that were created canonically if the diagram happens to be closed and then re-opened. (21) Rework the CanonicalStateListener to support injection of refresh 'pokes' to trigger updates in other dependents, such as the Properties view, when change in canonical activation is detected for any reason. (22) New JUnit tests for: - undo of semantic model change that created a canonical view after canonical edit policy disabled by CSS and close/reopen of the diagram - canonical edit policy's book-keeping does not leak diagram views nor model elements (23) CanonicalStateListener should be auto-retained because it automatically installs itself, and it won't be uninstalled except when successfully released. (24) Fix layout (margins etc.) of Synchronization properties group. (25) Fix concurrent modification in iteration over diagram edit part tree. Rationalize state-transition logic in canonical edit policy. (26) Fix some problems in canonical composite structures (incomplete): - manage connections canonically on border items as well as top shapes - do not include connectors as semantic children of structured classifiers but only as connections/edges of their connected elements - do not create parts of Association type when dropping an Association onto a structured classifier - include notation context in children-strategy query to account for structures such as part-with-port in connectors to disambiguate repeated semantic elements - add canonical composite structure tests (one still failing) (27) Refactor the canonical children strategies extension point ID to make it more meaningful and less redundant. Shave some execution time off the execution of the canonical edit policy tests in the automated build environment where we don't need to see what is happening in the diagrams. This involves a refactoring of earlier infrastructure that detects the build server or local Maven/Tycho build environment. (28) Fix failure to create canonical connection views because source/target nodes that were created canonically don't yet have their edit-parts. The canonical creation of connections is now deferred using the transaction pre-commit executor, exposed as a new DiagramHelper::submit(...) API. Several JUnit tests need updating, both to correct erroneous assumptions on latent bugs now fixed, and also to add UI event-processing in undo/redo scenarios to account for deferred connection creation. Use a DeferredLayoutCommand to improve the layout of the contents added to shape compartments by canonical 'drop', which otherwise would all be stacked on top of one another. Add a new pluggable strategy for determination of the edit-part that should handle creation of views, for cases such as flows in activities where connections must be dropped into contents compartments, not onto either the source or target node shape. (29) Fix canonical presentation of activity flows on pins. Implement basics of canonical synchronization of state machine diagrams. (30) Communication diagram synchronization of messages between lifelines. Requires a new extension interface for pluggable view-children strategies, to complement the semantic-children strategies, because the views that need to be synchronized are labels of connected edges, not the edges themselves. The semantic-children strategy interface is refactored to align with the new visual-children strategy interface, and likewise the determination of existing semantic and visual children in the PapyrusCanonicalEditPolicy. This also removes redundant re-calculation on semantic node children in the second-phase processing of connections. (31) Fix exceptions in synchronization and layout of communication diagrams. Fix regression in canonical deletion of edges. (32) Fix spurious deactivation of canonical edit policy in edit-parts that had had canonical mode (refresh enablement) toggled during execution of some user command. Change-Id: I9c39f74638cb55455e2d8bc42b07e49501ec3ea7
2015-03-07Bug 461432: [CSS] Drag-and-drop to reference a stylesheetChristian W. Damus1-6/+23
https://bugs.eclipse.org/bugs/show_bug.cgi?id=461432 Do not drop stylesheets that are already referenced by the diagram.
2015-03-05Bug 461432: [CSS] Drag-and-drop to reference a stylesheetChristian W. Damus3-1/+132
https://bugs.eclipse.org/bugs/show_bug.cgi?id=461432 Support drag-and-drop of CSS stylesheets onto diagrams. Change-Id: I45c424b39ae60856a389639653f1d8140cdfadcb
2014-10-28440230: [All Diagrams] Add Margins to the LabelsCéline Janssens1-5/+10
https://bugs.eclipse.org/bugs/show_bug.cgi?id=440230 Margin and Labels on Mars Change-Id: If62f1665a4697b422df8dc0ffc84c7e95bb659f9 Signed-off-by: Céline Janssens <Celine.Janssens@all4tec.net>
2014-09-25440230: [All Diagrams] Add Margins to the LabelsCéline Janssens1-5/+10
https://bugs.eclipse.org/bugs/show_bug.cgi?id=440230 - Generation of Component Diagram in order to make the PortNameEditPart a PapyrusWrappingLabel instead of WrappingLabel - Application of new Formatter and Clean up of Component Diagram sources - Change default value of Margin to 0 pixel - Switch horizontal/vertical to be aligned with the margin direction - add NON-NLS tag - fix some Cast Exception Change-Id: I6e222e5d8eb39ca5525e6747e7c0b18bd1089302 Signed-off-by: Céline Janssens <Celine.Janssens@all4tec.net>
2014-09-15[Releng] Update feature versions to 1.1.0Camille Letavernier1-2/+2
2014-09-15[Releng] Change plug-ins version to 1.1.0Camille Letavernier1-16/+16
2014-08-26[Code Style] Configure code style in the projectsChristian W. Damus2-0/+352
Configure the master settings for Code Style in the org.eclipse.papyrus.infra.core plug-in, including: - Code Formatter - Code Clean-up - Code Templates - Import Sort Order Employ the Oomph Project Configuration tooling to propagate these settings to all other Papyrus main, test, and developer plug-ins, plus the CDO Integration plug-ins. Update the Papyrus Oomph model to remove the workspace-wide code style settings. Change-Id: Id1c7c7fb94c82974a9f1c7cafcfcf32b71ce6c1f
2014-08-26442185: [CSS] NPE when trying to edit a local themeGabriel Pascual2-3/+13
https://bugs.eclipse.org/bugs/show_bug.cgi?id=442185 - Add behavior for CSS Theme edition starting from CSS file selection when there is no workspace theme Change-Id: I9c1d5c2a5ee9ea8c1cdf0b04a7d12134ecabe32a Signed-off-by: Gabriel Pascual <gabriel.pascual@all4tec.net>
2014-08-25[Code style] Apply clean-up profile to Papyrus Main plug-insCamille Letavernier6-12/+8
2014-08-21[Code style] Apply clean-up and formatter on Main plug-insCamille Letavernier33-590/+594
2014-08-20[Releng] Update Papyrus version to 1.0.1 in pom.xmlCamille Letavernier1-2/+2
2014-08-20[Releng] Update versions to 1.0.1Camille Letavernier1-18/+20
2014-08-07417409: [Performances - Properties view] Delay in UI when reorganizing ↵Christian W. Damus4-26/+26
diagram layout. https://bugs.eclipse.org/bugs/show_bug.cgi?id=417409 Make property sheet views reusable, with updating of the bound selection when the selection changes to another element that shows the same views. This employs new capability of the DataSource to update the selection that it encapsulates, pushing the new selection into the ModelElements that it creates, using a new delegating observable framework. Property sheet controls are re-used on a per-tab basis. Because of the new delegation pattern introduced here, we need to be able to ensure that delegate observables are disposed of when they are no longer needed. This includes not only the delegates of the new DelegatingObservables, but also the delegates of MultipleObservableValue and similar aggregates. As these delegates can be shared amongst multiple wrappers of different kinds, we use a simple reference counting scheme to ensure that observables are not disposed while they are still in use. This averts the exceptions discovered in multi-observable (multiple selection) scenarios on a previous iteration of this patch set. Change-Id: Ide8f3fcea4228083a68bc9d5d39dc5a50217af62
2014-06-04[Releng] Remove the (Incubation) suffix from all (main) plug-ins andCamille Letavernier1-1/+1
features Update the Bundle test accordingly
2014-05-15429642: [Model / CSS] Add properties view to define Model's stylesheetsCamille Letavernier1-1/+4
https://bugs.eclipse.org/bugs/show_bug.cgi?id=429642 - Fix NPE when some diagrams are deleted
2014-05-13429642: [Model / CSS] Add properties view to define Model's stylesheets Mickael ADAM2-22/+17
Patch Set 1: - Remove com.google.common.base.Optional Change-Id: I49a646f2fe1a59530f32b4302f2df598de10fd7f Task-Url: https://bugs.eclipse.org/bugs/show_bug.cgi?id=429642 Signed-off-by: Mickael ADAM <mickael.adam@ALL4TEC.net>
2014-04-30430079: [CSS] Papyrus shall provide features to define local themeCamille Letavernier2-28/+31
https://bugs.eclipse.org/bugs/show_bug.cgi?id=430079 - Minor fix on file extensions for images
2014-04-30430079: [CSS] Papyrus shall provide features to define local themeGabriel Pascual14-155/+3767
https://bugs.eclipse.org/bugs/show_bug.cgi?id=430079 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 <gabriel.pascual@all4tec.net>
2014-04-29429642: [Model / CSS] Add properties view to define Model's stylesheetsChristian W. Damus1-5/+4
https://bugs.eclipse.org/bugs/show_bug.cgi?id=429642 Add missing e4 CSS Core dependency required by the build.
2014-04-29429642: [Model / CSS] Add properties view to define Model's stylesheetsChristian W. Damus1-1/+1
https://bugs.eclipse.org/bugs/show_bug.cgi?id=429642 Fix Guava dependency version.

Back to the top