diff --git a/sirius/doc/Release_Notes.html b/sirius/doc/Release_Notes.html index 8b0aa73..1b949f1 100644 --- a/sirius/doc/Release_Notes.html +++ b/sirius/doc/Release_Notes.html @@ -7,13 +7,13 @@ -

Release Notes for Sirius

+

Release Notes for Sirius Desktop

  1. - Release Notes for Sirius + Release Notes for Sirius Desktop
    1. - Changes in Sirius 7.3.0 + Changes in Sirius Desktop 7.4.0
      1. User-Visible Changes @@ -27,7 +27,7 @@

        Release Notes for Sirius

    2. - Changes in Sirius 7.2.1 + Changes in Sirius 7.3.0
      1. User-Visible Changes @@ -41,7 +41,7 @@

        Release Notes for Sirius

    3. - Changes in Sirius 7.2.0 + Changes in Sirius 7.2.1
      1. User-Visible Changes @@ -55,7 +55,7 @@

        Release Notes for Sirius

    4. - Changes in Sirius 7.1.0 + Changes in Sirius 7.2.0
      1. User-Visible Changes @@ -69,18 +69,32 @@

        Release Notes for Sirius

    5. - Changes in Sirius 7.0.4 + Changes in Sirius 7.1.0
      1. User-Visible Changes
        2. +
      2. + Specifier-Visible Changes +
        3. +
      3. + Developer-Visible Changes +
        4. +
      +
      6. +
    6. + Changes in Sirius 7.0.4 +
        +
      1. + User-Visible Changes +
    7. Changes in Sirius 7.0.3
      1. - Developer-Visible Changes + Developer-Visible Changes
      8. @@ -88,10 +102,10 @@

      Release Notes for Sirius

      Changes in Sirius 7.0.2
      1. - Specifier-Visible Changes + Specifier-Visible Changes
      2. - Developer-Visible Changes + Developer-Visible Changes
      @@ -99,7 +113,7 @@

      Release Notes for Sirius

      Changes in Sirius 7.0.1
      1. - Developer-Visible Changes + Developer-Visible Changes
      @@ -107,10 +121,10 @@

      Release Notes for Sirius

      Changes in Sirius 7.0.0
      1. - User-Visible Changes + User-Visible Changes
      2. - Developer-Visible Changes + Developer-Visible Changes
      @@ -118,10 +132,10 @@

      Release Notes for Sirius

      Changes in Sirius 6.6.0
      1. - User-Visible Changes + User-Visible Changes
      2. - Developer-Visible Changes + Developer-Visible Changes
      @@ -129,7 +143,7 @@

      Release Notes for Sirius

      Changes in Sirius 6.5.1
      1. - Developer-Visible Changes + Developer-Visible Changes
      @@ -137,13 +151,13 @@

      Release Notes for Sirius

      Changes in Sirius 6.5.0
      1. - User-Visible Changes + User-Visible Changes
      2. - Specifier-Visible Changes + Specifier-Visible Changes
      3. - Developer-Visible Changes + Developer-Visible Changes
      @@ -153,16 +167,196 @@

      Release Notes for Sirius

      This document contains the release notes for recent major releases of Sirius. See also the release notes from previous versions for details about older releases.

      -

      Changes in Sirius 7.3.0

      +

      Changes in Sirius Desktop 7.4.0

      User-Visible Changes

        -
      • Added A new preference has been added in the Sirius Diagram preference page. This preference allows the user to choose the arrangement of elements created on a diagram when they are not directly positioned by the user. In the preference page, users can choose between a diagonal, vertical or horizontal arrangement.
        • +
      • Added Copy and paste style from one diagram element to another. The copied and pasted diagram elements may be of different types. The style properties are applied at best. You can refer to the + paste style documentation for more details. +
        • +
      • Modified The 3 other existing pastes ( + Paste Format, + Paste Style and + Paste Layout) are now called semantic paste (i.e. + Paste Format (Semantic), + Paste Style (Semantic) and + Paste Layout (Semantic)), but their behavior remains unchanged. +
        • +
      • Removed Feature + Apply the applicable appearance properties of the last selected shape to the other selected shapes. has been removed. Use the new style copy-paste feature, which does the same thing. +
        • +
      • Added A checkbox to ignore the pinning of elements on the diagram for the layout actions.
        • +
      • Added A new layout action to layout the direct children of the selection on a diagram.
        • +
      • Modified The layout of border nodes is now available for the selection (in addition to the whole diagram).
        • +
      • Modified Arrange actions have been renamed from “Arrange <...>” to “Layout <...>”.
        • +
      • Modified The pin and unpin actions are now combined into a single checkbox action.
        • +
      • Modified The preference for marking moved items as pinned is now disabled by default. You can re-enable it via Window > Preferences > Sirius > Sirius Diagram
        • +
      • Modified In Sirius table, font type and default size are now based on Preferences Settings of + General > Appearance > Colors and Fonts. Previously, cells font were always ‘Arial’ and of size ‘9’ but column and line headers were based on Preferences Settings. +
        • +
      • Modified In Sirius table, default colors has been changed to use Preferences Settings and selection coloring behaves like other Views and Editors. Previously, line headers were forced to gray, selected cell was using Menu color instead of Theme color and no color was indicating the row on mouse hover.
        • +
      • Added A new + color selection popup dialog has been defined to choose the color(label, fill and line) to use for the selected element. This popup dialog is opened from the diagram toolbar, the contextual menu, the Diagram navigation bar, or the Appearance tab in the Properties View. Four color categories has been defined in this popup: +
          +
        • Last Used colors category displays the ten last colors used by the user. These colors are persisted in preferences for the user workspace.
          • +
        • Custom colors category displays the ten first colors defined by the user. These colors are persisted in aird file. The “More...” button opens a dialog for adding custom colors.
          • +
        • Suggested colors category displays the ten “preferred colors” chosen by the user which are a subset of the colors defined in the VSM. These colors are persisted in the aird file. The “More...” button opens a dialog that lets the user choose the ten “preferred colors”.
          • +
        • Basic colors category displays ten useful colors.
          • +
        +
        • +
      • Modified Diagram export as SVG image has been improved. It is now repeatable as long as resources are the same. Previously some XML ID were generated using random mechanism.

      Specifier-Visible Changes

      +
        +
      • Modified Upgraded ELK version from 0.7.1 to 0.9.0, see the + ELK documentation for the list of changes in that version (and previous). Due to improvements or refactoring in ELK, some configuration option identifiers have been renamed or deleted. An automatic migration has been added in Sirius to migrate these identifiers used in VSM (see Migrations section for detail). In any case, if your modeler uses an ELK layout, you must be careful. +
        • +
      • Modified In tables, expressions and tools are injected with more variables. ‘table’, ‘containerView’ and ‘line’ elements are now accessible. With those elements, Specifier can access, for example, to + AnnotationEntry elements of + DTable instances. This modification allows following use-cases: +
          +
        • Create virtual lines: lines to group elements in tree with criteria based on attributes values or on user query.
          • +
        • Have columns unrelated to root element: for example, in Cross Table, columns targeting Ecore features to have a table with a dynamic number of columns.
          • +
        • Store states to alter tools: read/write mode driven by tools; default values to use in creation tools of current table.
          • +
        +
        • +
      • Modified The SquareDescription can now have -1 value for height and width. If the value -1 is used for both width and height enable the “auto-size” mode.
        • +

      Developer-Visible Changes

      +
        +
      • Removed AbstractTabbarContributor.createCopyAppearancePropertiesContribution and TabbarContributionFactory.createCopyAppearancePropertiesContribution has been removed.
        • +
      • Added The SiriusStyleClipboard singleton to store the style clipboard data for the diagram elements.
        • +
      • Added The ISimpleAuthorityListener functional interface to listen for any lock change, like IAuthorityListener but with a single method.
        • +
      • Modified ArrangeBorderNodesAction.initAction now has two parameters for its text: when there is no selection, when there is a selection.
        • +
      • Added Method + org.eclipse.sirius.diagram.business.api.diagramtype.IDiagramDescriptionProvider.allowsAutoSizeNodeStyle(DNode) has been added to indicates if a diagram description provider allows node auto-size mode computed from the node style on the specified element. +
        • +
      • Added Method + org.eclipse.sirius.diagram.business.api.query.DNodeQuery.isAutoSize() has been added to indicates if a node is in auto-size mode. +
        • +
      • Added Method + org.eclipse.sirius.diagram.business.api.query.DNodeQuery.supportNodeStyleAutoSize(NodeStyle, NodeStyleDescription) has been added to indicates if a DNode can support autosize mode defined from its style. +
        • +
      +

      Changes in + org.eclipse.sirius +

      +
        +
      • Added + org.eclipse.sirius.business.api.logger.InterpretationContext is created to ease setting and clearing variables when interpreting expressions. +
        • +
      +

      Changes in + org.eclipse.sirius.table +

      +
        +
      • Added + org.eclipse.sirius.table.business.api.helper.TableVariablesHelper is added to initialize variable value according active table decorator. +
        • +
      • Added + org.eclipse.sirius.table.business.api.helper.TableToolHelper is added to handle common evaluations with table tools. +
        • +
      • Modified The + org.eclipse.sirius.table.business.api.helper.TableHelper.canEditCrossTableCell(DCell) and + org.eclipse.sirius.table.business.api.helper.TableHelper.canEditCrossTableCell(DCell) have been deprecated for removal. + TableToolHelper should be used to handle precondition evaluation. +
        • +
      • Modified The + org.eclipse.sirius.table.business.api.query.DLineQuery query has been deprecated for removal. It was only used once in a internal class. +
        • +
      • Modified Methods + org.eclipse.sirius.table.tools.api.command.ITableCommandFactory.buildCreateLineCommandFromTool(LineContainer, EObject, CreateTool) and + org.eclipse.sirius.table.tools.api.command.ITableCommandFactory.buildCreateColumnCommandFromTool(DTable, EObject, CreateTool) have been deprecated for removal. They have been replaced by methods using applicable DSemanticDecorator in signature. +
        • +

      Changes in org.eclipse.sirius.diagram.ui

      +
        +
      • Added The constant + org.eclipse.sirius.diagram.ui.business.api.view.SiriusLayoutDataManager.KEEP_FIXED has been added to tag elements to be laid out and indicate that their location should not be modified. +
        • +
      • Added Method + org.eclipse.sirius.diagram.ui.business.api.view.SiriusLayoutDataManager.getArrangeCreatedViewsCommand(List<IAdaptable>, List<IAdaptable>, IGraphicalEditPart, String) has been added to handle the new + KEEP_FIXED layout tag. There are now 3 types of tags that can be used for layout: + org.eclipse.gmf.runtime.diagram.ui.services.layout.LayoutType.DEFAULT, + org.eclipse.sirius.diagram.ui.business.api.view.SiriusLayoutDataManager.LAYOUT_TYPE_ARRANGE_AT_OPENING and + org.eclipse.sirius.diagram.ui.business.api.view.SiriusLayoutDataManager.KEEP_FIXED. +
        • +
      • Added New preferences have been added to store the last colors used by the user: +
          +
        • + org.eclipse.sirius.diagram.ui.tools.api.preferences.SiriusDiagramUiPreferencesKeys.PREF_FONT_LAST_USED_COLORS is used to store the last used font colors. +
          • +
        • + org.eclipse.sirius.diagram.ui.tools.api.preferences.SiriusDiagramUiPreferencesKeys.PREF_FILL_LAST_USED_COLORS is used to store the last used fill colors. +
          • +
        • + org.eclipse.sirius.diagram.ui.tools.api.preferences.SiriusDiagramUiPreferencesKeys.PREF_LINE_LAST_USED_COLORS is used to store the last used line colors. +
          • +
        +
        • +
      • Added The method + org.eclipse.sirius.diagram.ui.tools.api.color.ColorManager.collectVsmColors(Session) has been added to collect colors defined in the VSM. +
        • +
      • Added The method + org.eclipse.sirius.diagram.ui.tools.api.color.ColorManager.rgbToString(RGB) has been added to convert an RGB color to a string. +
        • +
      • Added The method + org.eclipse.sirius.diagram.ui.tools.api.color.ColorManager.stringToRGB(String) has been added to convert a string color to an RGB color. +
        • +
      • Added The method + org.eclipse.sirius.diagram.ui.tools.api.color.ColorManager.sortColors(Collection<RGB>) has been added to sort a collection of RGB colors using their HSB (Hue, Saturation, Brightness). The specified collection isn’t modified. +
        • +
      +
        +
      • Added The class + org.eclipse.sirius.diagram.ui.tools.api.color.ColorCategoryManager has been added to manage color categories used in the new + ColorPalettePopup. It includes the following methods: +
          +
        • + org.eclipse.sirius.diagram.ui.tools.api.color.ColorCategoryManager.getLastUsedColors() to get the list of last colors used by the user. +
          • +
        • + org.eclipse.sirius.diagram.ui.tools.api.color.ColorCategoryManager.getCustomColors() to get the list of custom colors defined by the user. +
          • +
        • + org.eclipse.sirius.diagram.ui.tools.api.color.ColorCategoryManager.getSuggestedColors() to get the list of the ten preferred colors defined in the VSM. +
          • +
        • + org.eclipse.sirius.diagram.ui.tools.api.color.ColorCategoryManager.getBasicColors() to get ten useful colors. +
          • +
        • + org.eclipse.sirius.diagram.ui.tools.api.color.ColorCategoryManager.addLastUsedColor(RGB) to add a color to the list of last used colors. +
          • +
        • + org.eclipse.sirius.diagram.ui.tools.api.color.ColorCategoryManager.setCustomColors(List<RGB>) to set the list of custom colors defined by the user. +
          • +
        • + org.eclipse.sirius.diagram.ui.tools.api.color.ColorCategoryManager.setSuggestedColors(List<RGB>) to set the list of the preferred suggested colors. +
          • +
        • + org.eclipse.sirius.diagram.ui.tools.api.color.ColorCategoryManager.getSelectedColorsByPropertyId() to get the list of colors used for all objects selected in the representation for a specific propertyId. +
          • +
        +
        • +
      +

      Migrations

      +
        +
      • Added A migration participant has been added to migrate ELK options used in VSM. Some have been renamed and some others have been removed. You should carefully read the information logged during this migration and the + ELK release notes to check if any manual adjustments need to be made. The corresponding version, stored in attribute version of description:Group of the odesign file, is + 15.4.0.202401051836. +
        • +
      +

      Changes in Sirius 7.3.0

      +

      User-Visible Changes

      +
        +
      • Added A new preference has been added in the Sirius Diagram preference page. This preference allows the user to choose the arrangement of elements created on a diagram when they are not directly positioned by the user. In the preference page, users can choose between a diagonal, vertical or horizontal arrangement.
        • +
      +

      Specifier-Visible Changes

      +

      Developer-Visible Changes

      +

      Changes in + org.eclipse.sirius.diagram.ui +

      • Modified The methods org.eclipse.sirius.diagram.ui.tools.api.util.GMFNotationHelper.getNotes(Diagram) and @@ -186,13 +380,13 @@

        Changes in diagramPreferences.putBoolean(SiriusDiagramUiPreferencesKeys.@PREF_NEWLY_CREATED_ELEMENTS_LAYOUT@, 2);

        Changes in Sirius 7.2.1

        -

        User-Visible Changes

        +

        User-Visible Changes

        • Modified Sequence diagrams are now correctly identified in the Sirius Session Details report (accessible with the “Properties” dialog on an aird file).
        • Modified When a semantic modification is made on a diagram (e.g. Drag and Drop of an element), the notes and texts attached to the element remain attached, and the notes and texts contained in the element are preserved as much as possible.
        • Modified When an element is deleted after drag and drop, its attached notes and texts are also removed if preference “Remove/hide note when the annotated element is removed/hidden” is enabled.
        -

        Specifier-Visible Changes

        +

        Specifier-Visible Changes

        • Modified Three system properties have been added to allow the enablement of layout customizations for Regions (containers whose parent has a Children Presentation attribute set to Horizontal Stack or Vertical Stack):
            @@ -217,8 +411,8 @@

            Specifier-Visible Changes

        -

        Developer-Visible Changes

        -

        Changes in +

        Developer-Visible Changes

        +

        Changes in org.eclipse.sirius.diagram.ui

          @@ -242,11 +436,11 @@

          Changes in

        Changes in Sirius 7.2.0

        -

        User-Visible Changes

        +

        User-Visible Changes

        • Modified Java 17 (or later) is now required to run Sirius.
        -

        Specifier-Visible Changes

        +

        Specifier-Visible Changes

        • Added New decorators are now available for the beginning and edge of edges: CirclePlus, @@ -257,12 +451,12 @@

          Specifier-Visible Changes

          InputArrowWithFillDiamondAndDot.
        -

        Developer-Visible Changes

        +

        Developer-Visible Changes

        • Modified Java 17 is required as BREE and source level.

        Changes in Sirius 7.1.0

        -

        User-Visible Changes

        +

        User-Visible Changes

        • Added In a tree editor, if the Shift key is pressed during using the @@ -290,7 +484,7 @@

          User-Visible Changes

        • Modified The Sirius Session Details report (accessible with the “Properties” dialog on an aird file) is updated to always show the dependencies even for a not opened Session. The general dependencies are computed from serialized data. The image project dependencies are computed from the opened session or from the serialized data if the Session is not opened. A button is available to update image project dependencies.
        • Modified The Copy action is now visible in the tabbar, of a diagram editor, when no diagram element is selected, before it was visible only when at least one diagram element is selected. And the drop-down menu for Paste actions is now visible in the tabbar, of a diagram editor, when at least one diagram element is selected, before it was visible only when no diagram element is selected.
        -

        Specifier-Visible Changes

        +

        Specifier-Visible Changes

        • Added The system property org.eclipse.sirius.ui.enableCreatedElementsConstraintInSelectElementsListener has been added to allow to ignore the “created elements” constraint when the @@ -309,14 +503,14 @@

          Specifier-Visible Changes

          aql:input.getContextSelections().
        -

        Developer-Visible Changes

        +

        Developer-Visible Changes

        • Added The interface org.eclipse.sirius.ecore.extender.business.api.permission.IPermissionAuthority now has a isFrozen(EObject) method. This is a status handled by the collaborative plugins, but this new API makes this status available for queries from Sirius core plugins.
        -

        Changes in +

        Changes in org.eclipse.sirius

          @@ -337,7 +531,7 @@

          Changes in org.eclipse.sirius.business.api.session.Session.getSharedMainDAnalysis() is added to get the DAnalysis that holds data and can be shared in some context such as CDO.

        -

        Changes in +

        Changes in org.eclipse.sirius.diagram.ui

          @@ -395,7 +589,7 @@

          Changes in org.eclipse.sirius.properties.core.api.SiriusInputDescriptor.getOriginalSelections().

        -

        Migrations

        +

        Migrations

        Changes in Sirius 7.0.4

        -

        User-Visible Changes

        +

        User-Visible Changes

        Minor release to avoid errors thrown during indirect deletion of edges whose label is selected (deletion done from outside the diagram editor or from a custom command).

        Changes in Sirius 7.0.3

        -

        Developer-Visible Changes

        +

        Developer-Visible Changes

        • Removed To ensure compatibility with Eclipse 2022-09, dependency to com.ibm.icu has been removed.

        Changes in Sirius 7.0.2

        -

        Specifier-Visible Changes

        +

        Specifier-Visible Changes

        • Added The variables edgeView and otherEnd are now also available during precondition evaluation of a reconnect tool. Before, these variables were available only during the reconnection tool execution.
        -

        Developer-Visible Changes

        -

        Changes in +

        Developer-Visible Changes

        +

        Changes in org.eclipse.sirius

          @@ -456,7 +650,7 @@

          Changes in

        Changes in Sirius 7.0.1

        -

        Developer-Visible Changes

        +

        Developer-Visible Changes

        Changes in Sirius 7.0.0

        -

        User-Visible Changes

        +

        User-Visible Changes

        • Added Some enhancement have been done about the images management.
            @@ -482,7 +676,7 @@

            User-Visible Changes

          • Modified It is now possible to move a regions container by moving one of its region with the “Ctrl” shortcut key pressed. In the same way, it is now possible to select a regions container by clicking on one of its region with the “Ctrl” shortcut key pressed.
          • Removed It is no longer possible to change the workspace image of a diagram element with an image from an internal plugin via the “Set style to workspace image” action. This functionality affects a very small part of the use cases. The new UI of the “Set style to workspace image” action does not support this advanced functionality. However, it is still possible to go through Properties > Style > Workspace Image, then paste the path of the internal plugin image.
          -

          Developer-Visible Changes

          +

          Developer-Visible Changes

          • Added Sirius core and dialects metamodels have been extracted in new .model plugins with minimum dependencies. Each new plugin is re-exported by the plugin which was the previous container of its metamodel. The base packages of the generated code has not been modified. Each API modification is listed in the corresponding plugin section. Additional dialect providers and extension providers might have to modify the path or references to Sirius .ecore and .genmodel files to reflect this change. The new plugins are: @@ -539,7 +733,7 @@

            Developer-Visible Changes

            org.eclipse.sirius.business.api.query.DRepresentationDescriptorQuery.DRepresentationDescriptorValidityAdapter.triggerRepresentationValidation(boolean) were also created. These new methods (with a parameter value true) can be used in tests, but should not be used by the “Model explorer” view otherwise there would be no more lazy loading of representations.
          -

          Changes in +

          Changes in org.eclipse.sirius

            @@ -664,7 +858,7 @@

            Changes in org.eclipse.sirius.diagram.business.internal.metamodel.helper.ContentHelper.getAllEdgeMappings(diagramDescription, false) alongside with the getAllNodeMappings and getAllContainerMappings methods.

          -

          Changes in +

          Changes in org.eclipse.sirius.diagram.ui

            @@ -798,7 +992,7 @@

            Changes in org.eclipse.sirius.tests.support.api.EclipseTestsSupportHelper.copyDirectory(String, String) have been added to ease to the copy of the test files from the test plugin to the junit workspace.

          -

          Migrations

          +

          Migrations

          • Added A migration participant has been added to repair size of GMF nodes with Workspace Image style description. A default size was set for this type of nodes, which resulted in graphical inconsistencies (see Bug 576423 - @@ -809,7 +1003,7 @@

            Migrations

          Changes in Sirius 6.6.0

          -

          User-Visible Changes

          +

          User-Visible Changes

           -

          Developer-Visible Changes

          +

          Developer-Visible Changes

          Changes in org.eclipse.sirius.diagram

          @@ -856,7 +1050,7 @@

          Changes in

      -

      Changes in +

      Changes in org.eclipse.sirius.diagram.ui

        @@ -864,7 +1058,7 @@

        Changes in org.eclipse.sirius.diagram.ui.edit.api.part.AbstractDDiagramEditPart.refreshChildren() has been overridden to redraw the edges figures according to the order of the GMF edges.

      -

      Migrations

      +

      Migrations

      • Added A migration participant has been added to set a changeId value for each DRepresentationDescriptor that did not have one. Some old models were missing the changeId attribute, which could lead to technical problems. The migration participant org.eclipse.sirius.diagram.ui.business.internal.migration.SetChangeIdMigrationParticipant sets a random changeId if it didn’t already exist. The corresponding version, stored in attribute version of viewpoint:DAnalysis of the aird file, is @@ -875,8 +1069,8 @@

        Migrations

      Changes in Sirius 6.5.1

      -

      Developer-Visible Changes

      -

      Migrations

      +

      Developer-Visible Changes

      +

      Migrations

      • Modified The migration participant org.eclipse.sirius.diagram.ui.business.internal.migration.NoteShapeDefaultLabelAlignmentMigrationParticipant has been updated to repair Notes with a potential wrong vertical label alignment. This problem can occur since Sirius 6.3.2 used in a collaborative environment, Obeo Designer Team Edition or Team For Capella for example. The corresponding version, stored in the attribute version of viewpoint:DAnalysis of the aird file, is @@ -884,7 +1078,7 @@

        Migrations

      Changes in Sirius 6.5.0

      -

      User-Visible Changes

      +

      User-Visible Changes

      • Added It is possible to override at the aird level both “Sirius/Do Refresh on representation opening” and “Sirius/Automatic refresh” preferences. To override the preferences, right-click on the aird file, select “Properties”, and in the dialog go to the “Sirius settings” section. The preferences are stored in the project scope and associated to the aird file. For more details, refer the @@ -894,7 +1088,7 @@

        User-Visible Changes

        documentation .
      -

      Specifier-Visible Changes

      +

      Specifier-Visible Changes

      • Added A new CellEditor tool is available for feature column mapping of edition table. It allows to define a specific @@ -920,7 +1114,7 @@

        Specifier-Visible Changes

      -

      Developer-Visible Changes

      +

      Developer-Visible Changes

      • Added It is now possible to keep semantic element traceability during the representation export. For now, this option is only supported for diagram SVG export. In this case, a new attribute diagram:targetSemanticId is added on SVG elements to reference the target semantic id on which the graphical element is based on. This option can be activated programmatically or by setting a preference. See the details below: @@ -947,7 +1141,7 @@

        Developer-Visible Changes

        ELK documentation for the list of changes in that version (and previous).
      -

      Changes in +

      Changes in org.eclipse.sirius

        @@ -978,7 +1172,7 @@

        Changes in new DRepresentationQuery(DRpresentation).isAutoRefresh() instead.

      -

      Changes in +

      Changes in org.eclipse.sirius.diagram.ui

        @@ -1016,7 +1210,7 @@

        Changes in org.eclipse.sirius.ext.gmf.runtime.editparts.GraphicalHelper.getAbsoluteBoundsWithoutLabelsIn100Percent(GraphicalEditPart) has been added to get the rectangle bounds without taking labels into account. This is used, in particular, to compute the bendpoints of an edge when the source or the target of the edge is an edge.

      -

      Migrations

      +

      Migrations

      • Added A migration participant has been added to repair rectilinear edges containing only one bendpoint. Bracket edges are not relevant. The corresponding version, stored in attribute version of viewpoint:DAnalysis of the aird file, is 14.5.0.202104070943. diff --git a/sirius/doc/developer/Sirius Developer Manual.html b/sirius/doc/developer/Sirius Developer Manual.html index e7231ce..2878ed5 100644 --- a/sirius/doc/developer/Sirius Developer Manual.html +++ b/sirius/doc/developer/Sirius Developer Manual.html @@ -71,7 +71,7 @@

        Sirius Developer Manual

      • - Provide custom arrange-all + Provide custom layout-all
      • diff --git a/sirius/doc/developer/extensions-provide_custom-arrange-all.html b/sirius/doc/developer/extensions-provide_custom-arrange-all.html index d5f1e09..29817ae 100644 --- a/sirius/doc/developer/extensions-provide_custom-arrange-all.html +++ b/sirius/doc/developer/extensions-provide_custom-arrange-all.html @@ -7,16 +7,16 @@ -

        Providing a custom diagram layout algorithm (“Arrange All”)

        +

        Providing a custom diagram layout algorithm (“Layout All”)

        1. - Providing a custom diagram layout algorithm ("Arrange All") + Providing a custom diagram layout algorithm ("Layout All")
          1. - The Arrange All functionality in short + The Layout All functionality in short
          2. - The Arrange All concept as implemented by GMF + The Layout All concept as implemented by GMF
            1. The views and edit parts @@ -43,8 +43,8 @@

              Providing a custom dia

          -

          The Arrange All functionality in short

          -

          The arrange-all functionality is available in Sirius diagram editors in the form of a button and a context menu:

          +

          The Layout All functionality in short

          +

          The layout-all functionality is available in Sirius diagram editors in the form of a button and a context menu:

          @@ -63,13 +63,13 @@

          The Arrange All functionality in shor org.eclipse.sirius.diagram.ui.layoutProvider and org.eclipse.sirius.diagram.ui.viewOrderingProvider as well as an API to ease the writing of your own layout algorithms and their usage in Sirius diagram editors.

          -

          This API reuse the GMF “Arrange All” API and augments it with features needed by Sirius layout algorithms like:

          +

          This API reuse the GMF “Layout All” API and augments it with features needed by Sirius layout algorithms like:

          • The need to take in consideration pinned diagram elements
          • The need to take in consideration bordered nodes connected to edges
          -

          The Arrange All concept as implemented by GMF

          -

          GMF provides basic API and implementations to ease the customization of the “Arrange All” mechanism. It also implements a complete algorithm that is based on the graphical elements.

          +

          The Layout All concept as implemented by GMF

          +

          GMF provides basic API and implementations to ease the customization of the “Layout All” mechanism. It also implements a complete algorithm that is based on the graphical elements.

          The top level type of this this API is ILayoutNodeProvider :

          @@ -95,7 +95,7 @@

          The Arrange All concept as imple provides operation is meant to return true if the class can arrange the diagram for the specified operation.

          The - layoutEditParts operations will return the commands that will actually be in charge of arranging the diagrams' edit parts. The first one takes the main container that is to be arranged while the latter accepts a list of edit parts to arrange. + layoutEditParts operations will return the commands that will actually be in charge of layouting the diagrams' edit parts. The first one takes the main container that is to be layouted while the latter accepts a list of edit parts to layout.

          The implementation of those three methods forms your layout algorithm.

          With this API comes an extension point @@ -123,7 +123,7 @@

          Sirius Layout providers

          Sirius defines and already uses various different layout providers in different contexts.

          Here is a list of all of those with a basic description of each:

          DefaultLayoutProvider
          -

          It is used by Sirius as entry point to dispatch arrange requests on a Sirius diagram to registered layout providers. The dispatch takes in consideration layout algorithm specified in the VSM and layout providers provided from the Sirius extension point +

          It is used by Sirius as entry point to dispatch layout requests on a Sirius diagram to registered layout providers. The dispatch takes in consideration layout algorithm specified in the VSM and layout providers provided from the Sirius extension point org.eclipse.sirius.diagram.ui.layoutProvider.

          LineLayoutProvider
          @@ -133,12 +133,12 @@
          GridLayoutProvider
          InlineEdgeLayoutProvider

          Lays out connections alongside their source and target nodes (useful on the sequence diagram for example).

          ArrangeSelectionLayoutProvider
          -

          This provider only purpose is to delegate arrangement to attached layout provider after having added information about not selected parts in the layout hint.

          +

          This provider only purpose is to delegate layout to attached layout provider after having added information about not selected parts in the layout hint.

          It is used for example with our composite layout providers to keep fixed the not selected parts and to avoid putting other selected parts on it when layouting.

          -

          It is used primary by default provider whenever the arrange-all action is called because the arrangement can be done on a selection and not on all diagram elements.

          +

          It is used primary by default provider whenever the layout-all action is called because the layout can be done on a selection and not on all diagram elements.

          ArrangeAllOnlyLayoutProvider
          -

          This provider is used to delegate layouting to attached provider only when an arrange-all is done on a diagram and not an arrange selection.

          -

          When used as primary provider, the arrange selection action is not available in the menu of a Sirius editor using this provider.

          +

          This provider is used to delegate layouting to attached provider only when a layout-all is done on a diagram and not a layout selection.

          +

          When used as primary provider, the layout selection action is not available in the menu of a Sirius editor using this provider.

          It is used for example in the OrderedTreeLayoutProvider where it does not make sense to make a tree of just some elements because the all concept is to have a complete tree representation.

          @@ -151,7 +151,7 @@
          CompoundLayoutProvider
          PinnedElementLayoutProvider can be attached to a compound instance. Then those providers are called in their attach order one after another to do their layouting parts. It avoids the composite provider to duplicate code to handle pinned elements.

          BorderedItemAwareLayoutProvider
          -

          This provider arranges all the bordered nodes which are connected to one edge. It reduces the path of the edge between each extremity. For example:

          +

          This provider layouts all the bordered nodes which are connected to one edge. It reduces the path of the edge between each extremity. For example:

          Becomes

          @@ -717,7 +717,7 @@
          LayoutOptionFactory
          DefaultLayoutProvider
          -

          This class contains the core layout algorithm. When a user calls an arrange-all on a diagram that will be configured to use your layout algorithm, an instance of this class is created. You will be given the parts to layout. Then it is your job to layout it as you want.

          +

          This class contains the core layout algorithm. When a user calls a layout-all on a diagram that will be configured to use your layout algorithm, an instance of this class is created. You will be given the parts to layout. Then it is your job to layout it as you want.

          For example, the ELK integration have the following:

          public class ELKLayoutNodeProvider extends DefaultLayoutProvider {
 
@@ -773,7 +773,7 @@ 
          org.eclipse.sirius.diagram
             clp.addProvider(new PinnedElementsLayoutProvider(cdtp));
             if (ENABLE_BORDERED_NODES_ARRANGE_ALL) {
                 // ArrangeSelectionLayoutProvider wrap all providers to manage
-                // the selected diagram element on diagram "Arrange all"
+                // the selected diagram element on diagram "Layout all"
                 AbstractLayoutProvider abstractLayoutProvider = BorderItemAwareLayoutProviderHelper.createBorderItemAwareLayoutProvider(clp);
                 this.layoutNodeProvider = new ArrangeSelectionLayoutProvider(abstractLayoutProvider);
             } else {
diff --git a/sirius/doc/i18n_changes.html b/sirius/doc/i18n_changes.html
index 5ab027a..e8497aa 100644
--- a/sirius/doc/i18n_changes.html
+++ b/sirius/doc/i18n_changes.html
@@ -11,8 +11,229 @@ 
          Translation Keys Changes
          
 		
          This document lists the changes in 
 			TranslatableMessage used for Sirius internationalization in each Sirius version.
 		
          
-		
          Translation Keys Changes in Sirius 7.0.7 (from Sirius 7.0.6)
          
+		
          Translation Keys Changes in Sirius 7.4.0 (from Sirius 7.3.0)
          
 		
          Message Keys Added
          
+		
            
+			
          • 
+				org.eclipse.sirius.tools.api.Messages.ImageManager_projectMembersFailure
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PasteStylePureGraphicalAction_commandLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PasteStylePureGraphicalAction_text
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PasteStylePureGraphicalAction_toolTipText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeAction_ArrangeAll_ActionLabelText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeAction_ArrangeAll_ActionToolTipText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeAction_toolbar_ArrangeAll_ActionLabelText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeAction_toolbar_ArrangeAll_ActionToolTipText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeAction_ArrangeSelection_ActionLabelText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeAction_ArrangeSelection_ActionToolTipText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeAction_toolbar_ArrangeSelection_ActionLabelText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeAction_toolbar_ArrangeSelection_ActionToolTipText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeBorderNodesAction_actionDiagramText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeBorderNodesAction_toolTipText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeBorderNodesAction_toolbarActionDiagramText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeMenuManager_Arrange_ActionLabelText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeMenuManager_Arrange_ActionToolTipText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.LayoutChildrenAction_commandLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.LayoutChildrenAction_menuText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.LayoutChildrenAction_toolbarText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.LayoutChildrenAction_tooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.MovePinnedElementsAction_text
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.MovePinnedElementsAction_toolTipText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PinElementsEclipseAction_tooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorManager_logErrorParsingRGB
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_customCategoryLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_customCategoryMoreButtonTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_customCategoryTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_basicCategoryLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_basicCategoryTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_lastUsedCategoryLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_lastUsedCategoryTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_moreButtonLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_suggestedCategoryLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_suggestedCategoryMoreButtonTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_suggestedCategoryTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorPalettePopup_title
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_addButtonLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_addButtonTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_customAllColorsTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_customColorsDialogTitle
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_groupAllCustomColorsLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_groupAllSuggestedColorsLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_groupDisplayedSuggestedColorsLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_removeButtonLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_removeButtonTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_suggestedAllColorsTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_suggestedColorsDialogTitle
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ColorSelectionDialog_suggestedDisplayedColorsTooltip
+			
            • 
+		
          
+		
          Message Values Changed
          
+		
            
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PasteFormatAction_commandLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PasteFormatAction_text
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PasteLayoutAction_commandLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PasteLayoutAction_text
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PasteStyleAction_commandLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PasteStyleAction_text
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeBorderNodesAction_commandLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeBorderNodesAction_toolTipDiagramText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.ArrangeBorderNodesAction_toolbarActionText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.PinElementsEclipseAction_text
+			
            • 
+		
          
+		
          Message Keys Removed
          
+		
            
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.SiriusCopyAppearancePropertiesAction_tooltipMessage
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.DiagramEditorContextMenuProvider_arrangeMenuText
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.UnpinElementsEclipseAction_text
+			
            • 
+		
          
+		
          Translation Keys Changes in Sirius 7.3.0 (from Sirius 7.2.1)
          
+		
          Message Keys Added
          
+		
            
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.DiagramGeneralPreferencePage_newlyCreatedElementsGroupLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.NewlyCreatedElements_diagonalLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.NewlyCreatedElements_diagonalTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.NewlyCreatedElements_horizontalLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.NewlyCreatedElements_horizontalTooltip
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.NewlyCreatedElements_verticalLabel
+			
            • 
+			
          • 
+				org.eclipse.sirius.diagram.ui.provider.Messages.NewlyCreatedElements_verticalTooltip
+			
            • 
+		
          
+		
          Translation Keys Changes in Sirius 7.0.7 (from Sirius 7.0.6)
          
+		
          Message Keys Added
          
 		
            
 			
          • 
 				org.eclipse.sirius.tree.ui.provider.Messages.AbstractDTreeItemRunnableWithProgress_emptyDTreeItemsParameter
@@ -30,7 +251,7 @@ 
            Message Keys Added
            
 				org.eclipse.sirius.tree.ui.provider.Messages.ExpandDTreeItemRunnableWithProgress_expandAllTreeItems
 			
            • 
 		
          
-		
          Message Keys Removed
          
+		
          Message Keys Removed
          
 		
            
 			
          • 
 				org.eclipse.sirius.tree.ui.provider.Messages.ExpandDTreeItemRunnableWithProgress_treeItemCollapsing
@@ -40,7 +261,7 @@ 
            Message Keys Removed
            
 			
            • 
 		
          
 		
          Translation Keys Changes in Sirius 7.0.2 (from Sirius 7.0.1)
          
-		
          Message Keys Added
          
+		
          Message Keys Added
          
 		
            
 			
          • 
 				org.eclipse.sirius.diagram.ui.provider.Messages.ChangeMassivelyImagePathDialog_newLabel
@@ -77,7 +298,7 @@ 
            Message Keys Added
            
 			
            • 
 		
          
 		
          Translation Keys Changes in Sirius 7.0.1 (from Sirius 7.0.0)
          
-		
          Message Keys Added
          
+		
          Message Keys Added
          
 		
            
 			
          • 
 				org.eclipse.sirius.diagram.ui.provider.Messages.SVGImageRegistry_LoadImageError
@@ -135,7 +356,7 @@ 
            Message Keys Renamed or Moved
      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.viewpoint.provider.Messages.AnalysisSelectorFilteredItemsSelectionDialog_labelProviderLocal @@ -171,7 +392,7 @@

        Message Keys Added

        org.eclipse.sirius.tools.api.Messages.DRepresentationDescriptorQuery_representationError_broken_fragment_path
      -

      Message Keys Removed

      +

      Message Keys Removed

      • org.eclipse.sirius.diagram.Messages.NodeMappingHelper_methodInvocationErrorMsg @@ -202,7 +423,7 @@

        Message Keys Removed

      Translation Keys Changes in Sirius 6.6.0 (from Sirius 6.5.0)

      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.diagram.sequence.ui.Messages.SequenceEMFCommandFactory_notSupportedZorderCommandsMessage @@ -250,9 +471,9 @@

        Message Keys Added

        org.eclipse.sirius.diagram.Messages.ZOrderRecordingCommand_notSameType
      -

      Message Keys Removed

      +

      Message Keys Removed

      Translation Keys Changes in Sirius 6.5.0 (from Sirius 6.4.0)

      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.diagram.ui.provider.Messages.RepairEdgesWithOneBendpointMigrationParticipant_edgesModified @@ -417,7 +638,7 @@

        Message Keys Added

        org.eclipse.sirius.viewpoint.Messages.SiriusPreferencesImpl_noProjectScope
      -

      Message Keys Removed

      +

      Message Keys Removed

      • org.eclipse.sirius.diagram.ui.provider.Messages.FormatData_illegalTarget @@ -436,7 +657,7 @@

        Message Keys Removed

      Translation Keys Changes in Sirius 6.4.0 (from Sirius 6.3.2)

      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.diagram.ui.provider.Messages.DDiagramEditorImpl_error_representationRefresh @@ -553,7 +774,7 @@

        Message Keys Added

        org.eclipse.sirius.viewpoint.provider.Messages.ViewpointsFolderInvalidItemImpl_invalidRepresentations_title
      -

      Message Keys Removed

      +

      Message Keys Removed

      • org.eclipse.sirius.diagram.ui.provider.Messages.DDiagramEditorImpl_diagramRefreshTitle @@ -563,14 +784,14 @@

        Message Keys Removed

      Translation Keys Changes in Sirius 6.3.2 (from Sirius 6.3.1)

      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.viewpoint.Messages.DRepresentationDescriptorQuery_representationError

      Translation Keys Changes in Sirius 6.3.1 (from Sirius 6.3.0)

      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.diagram.ui.provider.Messages.BundledImageShape_idMissing @@ -594,14 +815,14 @@

        Message Keys Added

        org.eclipse.sirius.viewpoint.provider.Messages.LogThroughActiveDialectEditorLogListener_wrongErrorMessageProvider
      -

      Message Keys Removed

      +

      Message Keys Removed

      • org.eclipse.sirius.diagram.ui.provider.Messages.DiagramConnectionsPreferencePage_enableOverrideLabel

      Translation Keys Changes in Sirius 6.1 (from Sirius 6.0)

      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.common.ui.Messages.MigrationUIUtil_askToSaveChanges @@ -721,7 +942,7 @@

        Message Keys Added

        org.eclipse.sirius.viewpoint.Messages.TechnicalUidMigrationParticipant_message
      -

      Message Keys Removed

      +

      Message Keys Removed

      • org.eclipse.sirius.diagram.ui.provider.Messages.LayoutingModeSwitchingAction_activate @@ -740,7 +961,7 @@

        Message Keys Removed

      Translation Keys Changes in Sirius 6.0 (from Sirius 5.1)

      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.diagram.ui.provider.Messages.DiagramGeneralPreferencePage_sizeGroupLabel @@ -923,7 +1144,7 @@

        Message Keys Added

        org.eclipse.sirius.viewpoint.Messages.ModelingModelProvider_satusUnsavedDataWillBeLost
      -

      Message Keys Removed

      +

      Message Keys Removed

      • org.eclipse.sirius.diagram.ui.provider.Messages.DiagramGeneralPreferencePage_scaleDiagramOnExport @@ -954,7 +1175,7 @@

        Message Keys Removed

      Translation Keys Changes in Sirius 5.1 (from Sirius 5.0)

      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.diagram.sequence.Messages.Range_wrongArgument @@ -1104,7 +1325,7 @@

        Message Keys Added

        org.eclipse.sirius.viewpoint.Messages.SessionFactoryImpl_ResourceTypeErrorMsg
      -

      Message Keys Removed

      +

      Message Keys Removed

      • org.eclipse.sirius.viewpoint.provider.Messages.DeleteRepresentationAction_message @@ -1120,7 +1341,7 @@

        Message Keys Removed

      Translation Keys Changes in Sirius 5.0 (from Sirius 4.1)

      -

      Message Keys Added

      +

      Message Keys Added

      • org.eclipse.sirius.common.acceleo.aql.business.Messages.AQLInterpreter_errorWithExpression @@ -1513,7 +1734,7 @@

        Message Keys Added

        org.eclipse.sirius.viewpoint.Messages.SessionInterpreter_evaluationError
      -

      Message Keys Removed

      +

      Message Keys Removed

      • org.eclipse.sirius.editor.properties.Messages.ImportingDefaultPropertiesViewDescriptionCommand_text diff --git a/sirius/doc/index.html b/sirius/doc/index.html index ae7639f..76f27c8 100644 --- a/sirius/doc/index.html +++ b/sirius/doc/index.html @@ -109,7 +109,7 @@

        Contents

        -

        Note: This documentation refers to the latest major release of Sirius, version 7.3. For documentation corresponding to previous releases, see 7.2.x, 7.1.x, 7.0.x, 6.6.x, 6.5.x, 6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.1.x, 5.0.x, 4.1.x, 4.0.x, 3.1.x, see 3.0.x, 2.0.x, 1.0.x, or 0.9.

        +

        Note: This documentation refers to the latest major release of Sirius, version 7.4. For documentation corresponding to previous releases, see 7.3.x, 7.2.x, 7.1.x, 7.0.x, 6.6.x, 6.5.x, 6.4.x, 6.3.x, 6.2.x, 6.1.x, 6.0.x, 5.1.x, 5.0.x, 4.1.x, 4.0.x, 3.1.x, see 3.0.x, 2.0.x, 1.0.x, or 0.9.

        For further information, please visit our website at www.eclipse.dev/sirius.

        diff --git a/sirius/doc/specifier/diagrams/Diagrams.html b/sirius/doc/specifier/diagrams/Diagrams.html index e4fc7d5..a54340f 100644 --- a/sirius/doc/specifier/diagrams/Diagrams.html +++ b/sirius/doc/specifier/diagrams/Diagrams.html @@ -228,21 +228,21 @@

        Use an ELK layout algorithm

        When using one of the ELK layout algorithms, there are some specificities in comparison with the other “standard” Sirius layout:

        • The pinned status is not considered. All pinned elements are layouted as if they are not pinned. ELK does not manage this kind of property and Sirius does not add post treatement that could break the layout result.
          • -
        • Arrange all : All elements are layouted. The top left coordinates of the bounding box of all elements is {20, 20} (same coordinates as the result of +
        • Layout all : All elements are layouted. The top left coordinates of the bounding box of all elements is {20, 20} (same coordinates as the result of Reset Origin action action).
            -
          • Even in case of scroll bars before the starting point of arrange all
            • +
          • Even in case of scroll bars before the starting point of layout all
          • -
        • Arrange selection on one container: This action layouts all its content, resizes it to display its content but does not change its location.
          • -
        • Arrange selection on several elements on the same level: This action layouts elements in relation to each other but by ignoring other brothers. Overlap with other brothers, not selected ones, is possible. The top left coordinates of the bounding box of all elements remain the same. +
        • Layout selection on one container: This action layouts all its content, resizes it to display its content but does not change its location.
          • +
        • Layout selection on several elements on the same level: This action layouts elements in relation to each other but by ignoring other brothers. Overlap with other brothers, not selected ones, is possible. The top left coordinates of the bounding box of all elements remain the same.
          • If elements are containers: In addition to above behavior, their contents are layouted and they are resized.
          • -
        • Arrange selection on a container and some of its children: The result of this action is the same as launching an arrange selection only on the container.
          • +
        • Layout selection on a container and some of its children: The result of this action is the same as launching a layout selection only on the container.

        To use these algorithm, first install the feature:

        @@ -1430,7 +1430,18 @@

        Size Properties

        Size Computation Expression if specified.
      • - Size Computation Expression: An expression used to dynamically compute the size of a graphical element. It is evaluated in the context of the target element, and should return an integer. + Size Computation Expression: An expression used to dynamically compute the size of a graphical element. It is evaluated in the context of the target element, and should return an integer. By default, the value 3 is used to define a size of 30 pixels for the graphic element. +
          +
        • For Containers, the -1 value can be used to enable the “auto size” mode at creation time, it works for all styles applicable to Containers.
          • +
        • For WorkspaceImage style, set -1 as Size Computation Expression to use the size of the image as the size of the graphic element.
          • +
        • For Nodes, a positive integer is expected. +
            +
          • There is a special case with Square Style and label position set to + node. Having -1 in both width and height will allow to auto-size the node according the size of the label. The size computation expression will be the minimum size. +
            • +
          +
          • +
      • Border Size Computation Expression: An expression which is used to dynamically compute the size of the border of graphical element. It is evaluated in the context of the target element, and should return the border size diff --git a/sirius/doc/specifier/diagrams/images/groupUsingAnExistingGroupOfDDiagramLayoutMenu.png b/sirius/doc/specifier/diagrams/images/groupUsingAnExistingGroupOfDDiagramLayoutMenu.png index b42b599..3c1303c 100644 Binary files a/sirius/doc/specifier/diagrams/images/groupUsingAnExistingGroupOfDDiagramLayoutMenu.png and b/sirius/doc/specifier/diagrams/images/groupUsingAnExistingGroupOfDDiagramLayoutMenu.png differ diff --git a/sirius/doc/user/diagrams/Diagrams.html b/sirius/doc/user/diagrams/Diagrams.html index e54451c..787fe5b 100644 --- a/sirius/doc/user/diagrams/Diagrams.html +++ b/sirius/doc/user/diagrams/Diagrams.html @@ -44,6 +44,14 @@

        Diagram Editors

    2. +
  2. + Editing style of elements +
      +
    1. + Edit element color +
      2. +
    +
  3. Moving elements
      @@ -57,7 +65,7 @@

      Diagram Editors

      Distribute elements
    1. - Newly created elements arrangement. + Newly created elements layout.
    2. Reset Diagram or Container Origin @@ -131,19 +139,22 @@

      Diagram Editors

  4. - Copy/paste of format + Copy/paste of format (Semantic)
    1. - Paste Layout + Paste Layout (Semantic)
    2. - Paste Style + Paste Style (Semantic)
    3. - Paste Format + Paste Format (Semantic)
    5. +
  5. + Paste style +
  6. Paste image from clipboard
    7. @@ -174,7 +185,7 @@

    Diagram Editors

    Standard mode
  7. - Layouting mode: arrange your diagrams without modifying semantic models + Layouting mode: layout your diagrams without modifying semantic models
  8. Visibility mode: change diagram element visibility without modifying semantic models @@ -416,6 +427,95 @@

    Compartments

    experimental structures of containers with compartmented compartments, the F3 shortcut also allows to disable the resize propagation to manually correct the computed layout and remove empty space ( experimental). This might occur when there are several levels of compartments without the same number of compartments on each level. The corrective resize can be done on the last compartments of each compartmented container (from bottom for vertical stacks and from right for horizontal stacks).

    +

    Editing style of elements

    +

    Using the Appearance tab in the Properties view, the style of elements can be modified. For Nodes or Containers, for example, the font style can be modified, as can the color of the element. It is also possible to use an image to modify the overall appearance of the element.

    +

    + +

    +

    You can also access these options from different locations in the user interface:

    +
      +
    • Via the diagram toolbar: + +
      • +
    +
      +
    • Via the contextual menu, in + Format: + +
      • +
    +
      +
    • Via the navigation bar, in + Diagram: + +
      • +
    +

    Edit element color

    +

    There are 3 menu item that allow to change the color of an element:

    +
      +
    • + Font Color menu allows you to change the font color of the label of the selected element(s). +
      • +
    • + Fill Color menu allows you to change the background color of the selected element(s). +
      • +
    • + Line Color menu allows you to change the border color of a Node or Container, or the color of the Edge for the selected element(s). +
      • +
    +

    When one of the color-change menus is clicked, a popup dialog with color palettes appears, allowing you to choose which color to apply among four categories provided: +
    + +

    +
      +
    • + Last used colors category displays the ten last colors used by the user. +
      • +
    • + Custom colors category displays the ten first colors defined by the user. Additional colors can be created by clicking on the “More...” button. Users can also reorder the set of custom colors, choosing which colors to display in the popup dialog. +
      • +
    • + Suggested colors category displays the ten “preferred colors” defined by the user which are a subset of the colors defined in the Viewpoint Specification Model (odesign). This category is not displayed if no colors are defined in the VSM. Users can modify their ten “preferred colors” by clicking on the “More...” button. Here’s an example of colors defined in the VSM: + +
      • +
    • + Basic colors category displays ten application-defined colors for use in most contexts. This color palette cannot be modified by the user. +
      • +
    +

    Note: The colors saved for “Custom” and “Suggested” categories are persisted + separately for “Font Color”, “Fill Color” and “Line Color”. This is useful because you usually different colors for label and background for example. +

    +

    Note: + Last used colors category is persisted in preferences, + Custom and + Suggested colors categories are persisted in the aird file. +

    +

    When clicking on the “More...” button of the + Custom color category, the “Custom Colors” dialog appears. +

    +
      +
    • The user can define new colors via the system dialog, by clicking on the Add button.
      • +
    • The Remove button is used to remove a color from the palette.
      • +
    • Colors can be reordered with drag-and-drop. The first ten colors in the palette will be displayed in the color selection popup dialog.
      • +
    • There’s no limit to the number of custom colors you can add but only ten are displayed in the popup dialog.
      • +
    • Clicking on the OK button will persist the changes in the color palette, and the selected color will be applied to the selected element(s).
      • +
    • Clicking on the Cancel button will cancel all changes made to the color palette. + +
      • +
    +

    When clicking on the “More...” button of the + Suggested color category, the “Suggested Colors” dialog appears. +

    +
      +
    • The user can only edit the “Displayed suggestions” section to define the ten “Preferred colors” to be displayed in the color selection popup dialog.
      • +
    • Double-click on a color in the “All suggestions” section to add it to “Displayed suggestions”. Dragging and dropping a color from “All suggestions” to “Displayed suggestions” also adds a color.
      • +
    • Double click a color in the “Displayed suggestions” or drag it to “All suggestions” to remove from the “Displayed suggestions” section.
      • +
    • The “Displayed suggestions” color palette can be reordered using drag & drop.
      • +
    • Clicking on the OK button will persist the changes in the “Displayed suggestions” color palette, and the selected color will be applied to the selected element(s).
      • +
    • Clicking on the Cancel button will cancel all changes made to the color palette. + +
      • +

    Moving elements

    There are specific shortcuts to change the move behavior:

      @@ -526,28 +626,28 @@
      First and last elements
    • the first element is the highest one (with its center at the minimum y coordinate). If several elements are aligned on middle, the leftmost one is the first.
    • the last element is the lowest one (with the bottom side with the maximum y coordinate). If several elements are aligned by middle, the rightmost one is the last.
    -

    Newly created elements arrangement.

    +

    Newly created elements layout.

    When elements in a diagram are not directly positioned by the user. By default, they are sequentially positioned in the center of the editor, diagonally. They can also be positioned vertically or horizontally by changing the preference in Sirius > Sirius Diagram > Newly created elements layout.
    - +

      -
    • Diagonal arrangement:
      • +
    • Diagonal layout:

    - +

      -
    • Vertical arrangement:
      • +
    • Vertical layout:

    - +

      -
    • Horizontal arrangement:
      • +
    • Horizontal layout:

    - +

    Reset Diagram or Container Origin

    This action is available within the diagram or containers contextual menu (“Reset Origin”) or via “M1” + “HOME” shortcut. @@ -1093,7 +1193,7 @@

    Port shifting and 'drag and drop'

    The port is dropped in the container above the mouse location and linked to its closest edge.

    -

    Copy/paste of format

    +

    Copy/paste of format (Semantic)

    It is possible to duplicate format of diagram elements, that is to say to replicate mutual organization and style of diagram elements from one diagram to another. This replication only applies to the same semantic elements between diagrams.
    By default, this copy/paste replicates the layout (x, y width and height) AND the style (colors, font, ...).

    @@ -1110,8 +1210,8 @@

    Copy/paste of format

    When an element format is copied, the format of all its children is also recursively copied (containers, nodes or border nodes). The format of the label and outgoing edges of all these elements, is also copied.

    -

    Paste Layout

    -

    The next picture shows the diagram where the layout will be replicated. The tool to paste layout is called “Paste Layout” and can be activated from the tab-bar or from the contextual menu (see +

    Paste Layout (Semantic)

    +

    The next picture shows the diagram where the layout will be replicated. The tool to paste layout is called “Paste Layout (Semantic)” and can be activated from the tab-bar or from the contextual menu (see Edit section).

    @@ -1125,7 +1225,7 @@

    Paste Layout

    Warning : This copy/paste operation copies exactly what you see on a diagram. When using low zoom level, some diagram elements can be twisted and the paste operation will duplicate theses twistings on the other diagram. Please, zoom in to reduce twistings.

    Two modes for paste layout
    -

    Since Sirius 7.1.0, there are 2 modes to paste the layout. At each execution of the action “Paste format” or “Paste layout”, a dialog is displayed to choose the mode.

    +

    Since Sirius 7.1.0, there are 2 modes to paste the layout. At each execution of the action “Paste format (Semantic)” or “Paste layout (Semantic)”, a dialog is displayed to choose the mode.

    @@ -1165,7 +1265,7 @@
    Similar locations in absolute coo

      -
    • Launch the action “Paste layout”, expected result: The absolute coordinates of each element are preserved.
      • +
    • Launch the action “Paste layout (Semantic)”, expected result: The absolute coordinates of each element are preserved.

    @@ -1189,7 +1289,7 @@

    Optimized locations by group

      -
    • Launch the action “Paste layout”, expected result: The origin of each group of brothers, in the target diagram, are preserved (as you can see with guide on the horizontal and vertical rulers). And the layout of brothers, in the target diagram, is applied relative to each other.
      • +
    • Launch the action “Paste layout (Semantic)”, expected result: The origin of each group of brothers, in the target diagram, are preserved (as you can see with guide on the horizontal and vertical rulers). And the layout of brothers, in the target diagram, is applied relative to each other.

    @@ -1207,7 +1307,7 @@

    Optimized locations by group

    • Select the diagram
      • -
    • Launch the action “Paste layout”, expected result: The layout of 4 functions are copied into RPL1 and RPL2. The origin of each group of functions is preserved.
      • +
    • Launch the action “Paste layout (Semantic)”, expected result: The layout of 4 functions are copied into RPL1 and RPL2. The origin of each group of functions is preserved.

    @@ -1220,7 +1320,7 @@

    Optimized locations by group

      -
    • Launch the action “Paste layout” successively with RPL1 and RPL2 selected, expected result: The result is slightly different. The layout of REC is applied to RPL1 (only its size is modified, the location remains the same) and the layout of their children are applied. The layout of REC is applied to RPL2 (only its size is modified, the location remains the same) and the layout of their children are applied.
      • +
    • Launch the action “Paste layout (Semantic)” successively with RPL1 and RPL2 selected, expected result: The result is slightly different. The layout of REC is applied to RPL1 (only its size is modified, the location remains the same) and the layout of their children are applied. The layout of REC is applied to RPL2 (only its size is modified, the location remains the same) and the layout of their children are applied.

    @@ -1243,13 +1343,13 @@

    Optimized locations by group

      -
    • Launch the action "Paste layout"
      • +
    • Launch the action "Paste layout (Semantic)"

    -

    Paste Style

    -

    The next picture shows the diagram where the layout will be replicated. The tool to paste style is called “Paste Style” and can be activated from the tab-bar or from the contextual menu (see +

    Paste Style (Semantic)

    +

    The next picture shows the diagram where the layout will be replicated. The tool to paste style is called “Paste Style (Semantic)” and can be activated from the tab-bar or from the contextual menu (see Edit section).

    @@ -1259,8 +1359,8 @@

    Paste Style

    -

    Paste Format

    -

    The next picture shows the diagram where the layout will be replicated. The tool to paste format is called “Paste Format” and can be activated from the tab-bar when the diagram is selected, from the contextual menu (see +

    Paste Format (Semantic)

    +

    The next picture shows the diagram where the layout will be replicated. The tool to paste format is called “Paste Format (Semantic)” and can be activated from the tab-bar when the diagram is selected, from the contextual menu (see Edit section) or through the Ctrl+Alt+Shift+V shortcut.

    @@ -1274,6 +1374,17 @@

    Paste Format

    +

    Paste style

    +

    The Paste Style button is used to copy the style from one diagram element to another. Elements can be in different diagrams, have different semantic elements, or even be of different types (for example, you can copy the style of a node to an edge), in which case style properties will be applied at best (some style properties may not be applied).

    +

    To copy a style from one element to another : +
    1. select the element whose style you wish to copy, +
    2. click on the Copy Style button in the toolbar or in the Edit submenu of the context menu, +
    3. select the elements to which the style is to be applied, +
    4. click on Paste Style in the toolbar or in the Edit submenu of the context menu. +

    +

    + +

    Paste image from clipboard

    It is also possible to paste an image from the clipboard to a node or container. To do this, copy the image in your clipboard, select a node and click on the button “Paste image from clipboard” (see picture below). The image is saved as a PNG file in the workspace, in an “images” folder and the selected element has a workspace image style that references this image.

    @@ -1282,10 +1393,10 @@

    Paste image from clipboard

    Diagram element pinning

    Introduction

    It is possible to mark specific elements in a diagram as having a fixed location so that they are not moved by the - Arrange All action. + Layout All action.

    -

    Diagram element pinning allows you to combine both methods: manually arranging the position and size of elements when it is important while still being able to call - Arrange All for the rest, without the risk of destroying your manual layouts. +

    Diagram element pinning allows you to combine both methods: manually layouting the position and size of elements when it is important while still being able to call + Layout All for the rest, without the risk of destroying your manual layouts.

    Pin/unpin actions

    The next picture shows a diagram with three persons.

    @@ -1293,7 +1404,7 @@

    Pin/unpin actions

    - Arrange All action lays out all diagram elements in order to produce the “best” layout. As we can see on the next picture, all diagram elements are moved. + Layout All action lays out all diagram elements in order to produce the “best” layout. As we can see on the next picture, all diagram elements are moved.

    @@ -1308,7 +1419,7 @@

    Pin/unpin actions

    Now John Doe and Jane Smith are pinned, a new - Arrange All action will preserve their locations. + Layout All action will preserve their locations.

    @@ -1327,8 +1438,8 @@

    Pin/unpin actions

  9. it is not possible to pin/unpin edges or compartments.

    10. Configuration

    -

    Every diagram elements that you move will be pinned by default and will need an unpin operation to be “moveable” again.

    -

    This default behavior can be changed in Eclipse preferences, as can be seen in the next picture.

    +

    You have a configuration to ensure that any diagram element you move is automatically pinned and will require an unpinning operation to be movable again by a layout.

    +

    This behavior can be enabled or disabled in Eclipse preferences, as shown in the following image:

    @@ -1370,8 +1481,8 @@

    Standard mode

    -

    Layouting mode: arrange your diagrams without modifying semantic models

    -

    When you only want to do layout operations (e.g. arrange a diagram by moving nodes or edges), you may modify the semantic models without paying attention. For example, when organizing bordered nodes, you may change the container of the semantic element, without wanting do so.

    +

    Layouting mode: layout your diagrams without modifying semantic models

    +

    When you only want to do layout operations (e.g. layout a diagram by moving nodes or edges), you may modify the semantic models without paying attention. For example, when organizing bordered nodes, you may change the container of the semantic element, without wanting do so.

    When this mode is enabled, the following operations are changed: