|
|
| (58 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| − | Since Papyrus 0.10 (Eclipse Kepler), Papyrus provides a new version of the tabular editors. This version replaces the previous version in Eclipse Luna. <br/>
| + | [https://help.eclipse.org/2020-09/nav/73_1_1_0 General Table Documentation (2020-09)] |
| − | Since Papyrus 1.1.0 (Eclipse Mars), Papyrus provides hierarchical table too.<br/>
| + | |
| | | | |
| − | =Vocabulary=
| + | [[Category:Papyrus]] |
| − | *category : in tree table, a category is a feature to listen : ownedAttributes for example.
| + | |
| − | *context : the element on which the table is created. Thhis word is used in this documentation and in the table metamodel
| + | |
| − | ***The context will often be used as parent element in case of creation of a new element inside a table.
| + | |
| − | ***The context is used in synchronized table to provide the rows, according to the implementation of the table
| + | |
| − | *depth : word used for tree table, its means the distance between the context of the table and the showed element. It starts to 0 with direct children's context.
| + | |
| − | *Drag and Drop (DnD) : the action to select an element with the mouse and to move it to another located, could be done in the same Eclipse View or from an Eclipse View to another one. Always inside the same instance of Eclipse
| + | |
| − | *DnD : see Drag And Drop
| + | |
| − | *owner : the graphical parent of the table. it is used in the Model Explorer View to display the table to the wanted location. After creating a new table, in the general case, the owner field has the same value than the root field. This word is used in the Property View of the table (see Viewpoint documentation for further information)
| + | |
| − | *root : the same thing than the context. This word is used in the Property View of the Table (see Viewpoint documentation for further information)
| + | |
| − | *type : the type of the table is given a a field string owned by the object TableConfiguration. This field is used by the Tabular editors to know how to open and manage the instance of the tables. The type of a table can't be changed by the user. Example of known types :
| + | |
| − | **PapyrusGenericTable : the type of UML Generic Table. This table is filled by DnD and accepts all UML Elements
| + | |
| − | **PapyrusSysMLRequirementTable : the type of the Table used to edit Requirement. This table is synchronized and shows only Class stereotyped by Requirements directly owned by the context of the table.
| + | |
| − | **PapyrusClassTreeTable : the type of the Class Tree Table. In this provided configuration, this table is fully synchronized. Its shows :
| + | |
| − | ***on first level (depth=0), the classes directly owned by the context of the table
| + | |
| − | ***on the second level (depth=1), the owned attributes, the owned operations and the nested classes of the classes displayed on the first level.
| + | |
| − | ***on the third level (depth=2), the parameters of the operations dsiplay on the the second level
| + | |
| − | | + | |
| − | = General presentation=
| + | |
| − | Papyrus provides tabular editors to allow to the user to edit their models with a new way as well than the Diagram editors and the Property View.
| + | |
| − | So, in the table, the user can create/destroy model's element and edit their features.
| + | |
| − | | + | |
| − | Papyrus provides to main kinds of tabular editors :
| + | |
| − | #normal table (also called flat table)
| + | |
| − | #tree table (also called hierarchical table)
| + | |
| − | | + | |
| − | Moreover the contents (most often the rows) of the table, can be synchronized on the context of the table.
| + | |
| − | | + | |
| − | ==Normal table and synchronization==
| + | |
| − | #Normal table can be synchronized or not, it depends of the type of the table. The switch between synchronization and no synchronization is not allowed.
| + | |
| − | #if the table is not synchronized, it is filled by the user using Drag and Drop. The user selects an element displayed in the Model Explorer and drop it into an opened table (in the row header area).
| + | |
| − | This action will create a new row, if the dropped element is allowed by the table implementation.
| + | |
| − | #if the table is synchronized, the user can't drop element to add rows. The rows are calculated according to the table context and the table implementation. The user can't change the allowed context of the rows.
| + | |
| − | | + | |
| − | ==Tree Table and synchronization==
| + | |
| − | The contents of the tree table is always synchronized, excepted for the first level (depth=0), which can be synchronized of filled by the user by Drag and Drop from the ModelExplorer, as for normal table.
| + | |
| − | The Tree Table provides a way to choose :
| + | |
| − | * the filling of the first level (DnD or synchronization)
| + | |
| − | * the number of levels (depths) to listen and what to listen
| + | |
| − | | + | |
| − | ==examples of table==
| + | |
| − | [[File:Normal_table.PNG|frame|none| an example of normal table (UML Generic table)]] <br> | + | |
| − | [[File:Multi_tree_table.PNG|frame|none| an example of tree table, with the hierarchy displayed on several columns, and categories visible (UML Tree Class table)]]<br>
| + | |
| − | [[File:Multi_hidden_categories_tree_table.PNG|frame|none| an example of tree table, with the hierarchy displayed on several columns, and categories hidden (UML Tree Class table)]]<br>
| + | |
| − | [[File:Single_tree_table.PNG|frame|none| an example of tree table, with the hierarchy displayed on one column, and categories visible (UML Tree Class table)]]<br>
| + | |
| − | <br>
| + | |
| − | | + | |
| − | = Existing Tables in small words =
| + | |
| − | * UML Generic Table
| + | |
| − | * SysML Allocation Table
| + | |
| − | * SysML Requirement Table
| + | |
| − | * Views Table
| + | |
| − | * UML Class Tree Table
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | == UML Generic Table ==
| + | |
| − | | + | |
| − | Elements Accepted : UML Element only (all of them)
| + | |
| − | | + | |
| − | Filling Way : User, by Drag&Drop from the Model Explorer
| + | |
| − | | + | |
| − | Possible Context : all UML Element.<br>
| + | |
| − | | + | |
| − | Save : All rows displayed in the table are saved in the model<br>
| + | |
| − | | + | |
| − | Element Creation : All UML Elements<br>
| + | |
| − | | + | |
| − | <br>
| + | |
| − | | + | |
| − | == SysML Allocation Table<br> ==
| + | |
| − | | + | |
| − | Elements Accepted : SysML Allocation only<br>
| + | |
| − | | + | |
| − | Filling Way : Automatic, by Synchronization on the context of the model. Only the Allocation directly owned by the context of the table are displayed.<br>
| + | |
| − | | + | |
| − | Possible Context : UML Package, with the SysML Profile Allocations applied.<br>
| + | |
| − | | + | |
| − | Save : The Rows are not serialized in the model, because they are derived of the UML Model.<br>
| + | |
| − | | + | |
| − | Element Creation : SysML Allocation<br>
| + | |
| − | | + | |
| − | <br>
| + | |
| − | | + | |
| − | == SysML Requirement Table ==
| + | |
| − | | + | |
| − | Elements Accepted : SysML Requirement only
| + | |
| − | | + | |
| − | Filling Way : Automatic, by Synchronization on the context of the model. Only the Requirements directly owned by the context of the table are displayed.<br>
| + | |
| − | | + | |
| − | Possible Context : UML Package, with the SysML Profile Requirement applied.<br>
| + | |
| − | | + | |
| − | Save : The Rows are not serialized in the model, because they are derived of the UML Model.
| + | |
| − | | + | |
| − | Element Creation : SysML Requirement<br>
| + | |
| − | | + | |
| − | <br>
| + | |
| − | | + | |
| − | == Views Table ==
| + | |
| − | *Elements Accepted : Papyrus Views (Table/Diagram/...) only
| + | |
| − | *Filling Way : Automatic, by Synchronization on the context of the model.
| + | |
| − | *Possible Context : All UML Elements<br>
| + | |
| − | *Save : The Rows are not serialized in the model, because they are derived of the notation Model.<br>
| + | |
| − | *Element Creation None
| + | |
| − | | + | |
| − | <br>
| + | |
| − | | + | |
| − | == UML Class Tree Table ==
| + | |
| − | * Element accepted : Classes (depth=0 and depth=1), Properties (depth=1), Operations (depth=1), Parameters (depth=2)
| + | |
| − | * Filling way : Automatic, synchronized on the context of the table
| + | |
| − | * Possible context : Package or Class
| + | |
| − | * Save : The rows are not serialized in the model, because they are derivied from the context of the classes
| + | |
| − | | + | |
| − | = Table Features<br> =
| + | |
| − | | + | |
| − | The table framework provides a large number of features. Here we will describe all existing features supported by the framework, but not necessarly by all the tables.<br>
| + | |
| − | | + | |
| − | #Edit Cell Values<br>
| + | |
| − | #Change Axis (Columns/Row) Order<br>
| + | |
| − | #Invert Axis (Exchange Column And Row)<br>
| + | |
| − | #Add Axis (Column/Row) Element by Drag&Drop from another view (ModelExplorer)<br>
| + | |
| − | #Remove Column/Row<br>
| + | |
| − | #Destroy Column/Row Element<br>
| + | |
| − | #Rename Column/Row Header<br>
| + | |
| − | #Choose the Displayed Columns/Rows<br>
| + | |
| − | #Choose the Displayed Columns/Rows for Stereotype Property in the popup menu<br>
| + | |
| − | #Paste Columns/Rows From External Spreadsheet<br>
| + | |
| − | #Display Index Column/Row Header<br>
| + | |
| − | #Display Label Column/Row Header<br>
| + | |
| − | #Configure Index Header Style (A, B, C...Z, AA, AB, ... or 0,1,2,3)<br>
| + | |
| − | #Configure Label Header Style : select the information to Display in the Header Label (Name, Multiplicity, Type, Icon, isDerived)<br>
| + | |
| − | #Export table into the Excel Format<br>
| + | |
| − | #Print table<br>
| + | |
| − | #Sort Column/Row Axis by Alphabetic order<br>
| + | |
| − | #Sort Rows selecting one or several column header<br>
| + | |
| − | #Save and restore Table Axis Configuration<br>
| + | |
| − | #Select All
| + | |
| − | #AutoResize axis<br>
| + | |
| − | | + | |
| − | === <br> ===
| + | |
| − | | + | |
| − | === Edit Cell Values ===
| + | |
| − | | + | |
| − | Double Click on a cell or selecting a cell then pressing F2, excepted for derived features<br>
| + | |
| − | | + | |
| − | === Change Axis Order<br> ===
| + | |
| − | | + | |
| − | Click on the axis to move and drop it to its new location.<br>
| + | |
| − | | + | |
| − | === Invert Axis<br> ===
| + | |
| − | | + | |
| − | Select the action Invert Axis in the popup menu or change it into the Table Property View.
| + | |
| − | | + | |
| − | === Add Axis (Column/Row) Element by Drag&Drop<br> ===
| + | |
| − | | + | |
| − | Select your element and drop it into the table, in the column region or in the row region to add it.<br>
| + | |
| − | | + | |
| − | === Remove Column/Row<br> ===
| + | |
| − | | + | |
| − | Select the header of the axis to remove then right click and select Remove Column/Row. The axis will be remove of the table, but the represented element will continue to be in the model.<br>
| + | |
| − | | + | |
| − | === Destroy Column/Row Element<br> ===
| + | |
| − | | + | |
| − | Select the header of the axis element to destroy then right click and select Destroy Column/Row Element. The represented element will be destroyed and its axis will be removed from the table.<br>
| + | |
| − | | + | |
| − | === Rename Column/Row Header<br> ===
| + | |
| − | | + | |
| − | This function can do 2 things according to the usecase : <br>
| + | |
| − | | + | |
| − | *Rename the element represented by the axis, when the element is owned by your model<br>
| + | |
| − | *Define an alias to the axis, when the element is not owned by your model (UML Feature for example)<br>
| + | |
| − | | + | |
| − | Select the header of the axis element to rename then right click and select Rename Header.<br>
| + | |
| − | | + | |
| − | === Choose the Displayed Columns/Rows<br> ===
| + | |
| − | | + | |
| − | Right click in the table (not in the header) and select Columns -> Create/Destroy Columns. (the same thing for rows<br>
| + | |
| − | | + | |
| − | === Choose the Displayed Columns/Rows for Stereotype Property in the popup menu<br> ===
| + | |
| − | | + | |
| − | Right click in the table (not in the header) and select Select Stereotype Properties Columns (or Rows)<br>
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | {| width="1007" cellspacing="1" cellpadding="1" border="1" align="center" summary="This table describes the feature of the table when the axis are NOT inverted."
| + | |
| − | |+
| + | |
| − | === Features/Tables, when the Axis are NOT inverted. ===
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | |-
| + | |
| − | | <br>
| + | |
| − | | valign="middle" align="center" | UML Generic Table<br>
| + | |
| − | | valign="middle" align="center" | SysML Allocation Table<br>
| + | |
| − | | valign="middle" align="center" | SysML Requirement Table<br>
| + | |
| − | | valign="middle" align="center" | Views Table<br>
| + | |
| − | |-
| + | |
| − | | Content synchronized on table context<br>
| + | |
| − | | valign="middle" align="center" | No<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | |-
| + | |
| − | | Edit Cell Value<br>
| + | |
| − | | valign="middle" align="center" rowspan="2" colspan="4" | Yes<br>
| + | |
| − | |-
| + | |
| − | | Change Axis Order<br>
| + | |
| − | |-
| + | |
| − | | Add Column Axis By Drag & Drop
| + | |
| − | | valign="middle" align="center" colspan="4" | No<br>
| + | |
| − | |-
| + | |
| − | | Add Row Axis By Drag & Drop
| + | |
| − | | valign="middle" align="center" | All UML Elements<br>
| + | |
| − | | valign="middle" align="center" rowspan="3" colspan="3" | No (Synchronized table)
| + | |
| − | |-
| + | |
| − | | Remove Column<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | |-
| + | |
| − | | Remove Row<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | |-
| + | |
| − | | Destroy Column Element<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Destroy Row Element<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | | valign="middle" align="center" | Yes<br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Rename Column Header<br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Rename Row Header<br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Choose the Displayed Columns<br>
| + | |
| − | | valign="middle" align="center" rowspan="2" colspan="3" | Yes
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Choose the Displayed Columns for Stereotype Property in the popup menu<br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Choose the Displayed Rows<br>
| + | |
| − | | valign="middle" align="center" | No<br>
| + | |
| − | | valign="middle" align="center" | No<br>
| + | |
| − | | valign="middle" align="center" | No<br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Choose the Displayed Rows for Stereotype Property in the popup menu<br>
| + | |
| − | | valign="middle" align="center" colspan="3" | No
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Paste Column From Spreadsheet<br>
| + | |
| − | | valign="middle" align="center" | No<br>
| + | |
| − | | valign="middle" align="center" | No<br>
| + | |
| − | | valign="middle" align="center" | No<br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Paste Row From Spreadsheet<br>
| + | |
| − | | valign="middle" align="center" colspan="4" rowspan="8" | Yes
| + | |
| − | |-
| + | |
| − | | Display Index Column/Row Header<br>
| + | |
| − | |-
| + | |
| − | | Display Label Column/Row Header<br>
| + | |
| − | |-
| + | |
| − | | Configure Index Header Style <br>
| + | |
| − | |-
| + | |
| − | | Configure Label Header Style<br>
| + | |
| − | |-
| + | |
| − | | Export to Excel<br>
| + | |
| − | |-
| + | |
| − | | Print table<br>
| + | |
| − | |-
| + | |
| − | | Sort Column Axis By Name<br>
| + | |
| − | |-
| + | |
| − | | Sort Row Axis By Name<br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |-
| + | |
| − | | Save and restore Table Axis Configuration<br>
| + | |
| − | | valign="middle" align="center" colspan="4" rowspan="2" | Yes
| + | |
| − | |-
| + | |
| − | | Select All <br>
| + | |
| − | |-
| + | |
| − | | AutoResize axis<br>
| + | |
| − | | valign="middle" align="center" colspan="4" | Yes<br>
| + | |
| − | |-
| + | |
| − | | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | | valign="middle" align="center" | <br>
| + | |
| − | |}
| + | |
| − | | + | |
| − | <br>
| + | |
| − | | + | |
| − | <br>
| + | |
| − | | + | |
| − | <br>
| + | |
| − | | + | |
| − | == Paste From Spreadsheet in a Table ==
| + | |
| − | === General===
| + | |
| − | *Tables support the paste from Spreadsheet (Excel for example).
| + | |
| − | *This feature is already configured for SysML Requirements Table and SysML Allocations Table.
| + | |
| − | *For Generic Table, the user must configure the paste himself.
| + | |
| − | *Stereotype application :
| + | |
| − | **If your table displays columns representing stereotype's properties, the required stereotypes will be applied if there is a value to paste in the cell.
| + | |
| − | **If you want force stereotype application on all pasted elements, you must use post-actions
| + | |
| − | *Name Resolution
| + | |
| − | ***Papyrus table tries to resolve the text pasted from the external spreadsheet. That is to say if the text is pasted in a column representing a boolean, text will be converted in boolean value, if the text is pasted in a column representing a UML NamedElement, we try to find this NamedElement in the exising model to set the value.
| + | |
| − | ***if the resolution of the pasted text failed, we create a CellProblem, to store the pasted value. This value is displayed in the table, underlined in red.
| + | |
| − | *If the pasted spreadsheet as more columns than the current table, the too many columns will be ignored.
| + | |
| − | *If the pasted spreadsheet as less columns than the current table there is no problem to do the paste.
| + | |
| − | *In the mixed case, some rows have too many columns and others not enough, there is no problem to do the paste.
| + | |
| − | | + | |
| − | ===Steps to paste in a Generic Table===
| + | |
| − | We assume that the user wants to paste rows (and not columns).
| + | |
| − | *Create a new Generic table
| + | |
| − | *Select the columns to display in your table.
| + | |
| − | *Select the table in the ModelExplorer View in order to display its Property View
| + | |
| − | *In the Property View goes into the Paste Tab. 4 informations must be completed by the user:
| + | |
| − | **Detached Mode (when <code>true</code>, paste is faster but actions done by service edit will be ignored.
| + | |
| − | ***if <code>false</code>, Paste action uses the service edit (initialize default values, apply stereotypes required by element id).
| + | |
| − | ***if <code>true</code>, stereotype required by the element id will be ignored.
| + | |
| − | **Pasted Element Id : defines the pasted element: org.eclipse.papyrus.uml.Class will create a UML Class
| + | |
| − | ***org.eclipse.papyrus.sysml.Requirement will create a uml.Class stereotyped Requirement, called Requirement0 if Detached mode=false.
| + | |
| − | ***org.eclipse.papyrus.sysml.Requirement will create a uml.Class the name will be initialized only if the user pastes a name value and the steroetype will be applied only if a column requires it or if it is defined by opst actions)
| + | |
| − | **ContainementFeature : the feature owning the pasted elements
| + | |
| − | **Post Actions : a way to define 2 kinds of actions:
| + | |
| − | ***actions done just after the element creation
| + | |
| − | ***actions done after have pasting all cell values
| + | |
| − | ***currently, Papyrus provides Post Action only for stereotype application
| + | |
| − | ***currently, Post Actions are ignored when detached mode=<code>false</code>
| + | |
| − | | + | |
| − | [[File:PasteInTablePropertyView.jpg |Paste In Table Configuration Property View]]
| + | |
| − | | + | |
| − | == Import From Spreadsheet in a Table (CSV File)==
| + | |
| − | The mecanism used for import in the same than for the Paste, so previous rules are always available.
| + | |
| − | In the popup menu of the table, you will find a menu called "Import From File". This menu allows to import a CSV file, managing the columns separators and the text delimiter.
| + | |
| − | [[File:ImportCSVDialog.jpg |Import Dialog - Configuring Import]]
| + | |
| − | | + | |
| − | == Table Property View<br> ==
| + | |
| − | | + | |
| − | The Property View of the table is accessible selecting the table in the ModelExplorer.<br>
| + | |
| − | | + | |
| − | <br>
| + | |
| − | | + | |
| − | == Synchronization between tables and model explorer ==
| + | |
| − |
| + | |
| − | === Generalities ===
| + | |
| − |
| + | |
| − | As illustrated below this feature is enabled when the <I>Link With Editor</I> button is activated : <br />
| + | |
| − | | + | |
| − | [[File:ModelExplorerLinkWithEditor.png|thumb|center|350px|ModelExplorerLinkWithEditor]] <br />
| + | |
| − | | + | |
| − | This link the active diagram, in the multi editor view, with the model explorer view. This link works bidirectionally. <br />
| + | |
| − | As shown below, more than one element can be selected in one view and their counterparts, if present in the other, will be automatically selected as well. <br />
| + | |
| − | | + | |
| − | [[File:SelectionWithDiagram.png|center|SelectionWithDiagram|thumb|350px]] <br />
| + | |
| − | | + | |
| − | <I>It is to be noted that, when changing pages, the selection for each of them remain in memory and handled by setInput in tabbedPropertySheetPage</I> <br /> <br />
| + | |
| − | | + | |
| − | === Row selections ===
| + | |
| − | | + | |
| − | The default behavior of the tables, and their representation, is to list the appropriate elements as rows with each property indicated by a column as illustrated below. <br />
| + | |
| − | | + | |
| − | {{multiple image
| + | |
| − | | width = 250
| + | |
| − | | align = center
| + | |
| − | | direction = horizontal
| + | |
| − | | image1 = GenericSelection.png
| + | |
| − | | caption1 = GenericSelection
| + | |
| − | | image2 = RequirementSelection.png
| + | |
| − | | caption2 = RequirementSelection
| + | |
| − | | image3 = AllocationSelection.png
| + | |
| − | | caption3 = AllocationSelection
| + | |
| − | | image4 = ViewsSelection.png
| + | |
| − | | caption4 = ViewsSelection
| + | |
| − | }}
| + | |
| − | {{clear}} <br />
| + | |
| − | | + | |
| − | === Column selections ===
| + | |
| − | | + | |
| − | The axis of the table can also be inverted and the elements represented as columns with their properties as rows : <br />
| + | |
| − | | + | |
| − | [[File:ColumnSelection.png|center|ColumnSelection|thumb|350px]] <br />
| + | |
| − | | + | |
| − | Both those selections are achieved either by clicking on the element in the model explorer or the element's row or Column tag in the table. <br />
| + | |
| − | | + | |
| − | === Cell selections ===
| + | |
| − | | + | |
| − | Wether the axis of the table is inverted or not, the user can select elements represented as cells inside a row or column of the table and see its counterpart selected as well. <br />
| + | |
| − | It is important to remember that the cell selection is a one way behavior, from cell to model explorer, as the table cannot know what the user wants to select, row or cell, based on a selection in the model explorer.<br/ >
| + | |
| − | | + | |
| − | {{multiple image
| + | |
| − | | width = 350
| + | |
| − | | align = center
| + | |
| − | | direction = horizontal
| + | |
| − | | image1 = CellSelection.png
| + | |
| − | | caption1 = CellSelection
| + | |
| − | | image2 = CellSelectionInvertAxis.png
| + | |
| − | | caption2 = CellSelectionInvertAxis
| + | |
| − | }}
| + | |
| − | {{clear}} <br />
| + | |
| − | | + | |
| − | === Mixed Selections ===
| + | |
| − | | + | |
| − | A behavior worthy of notice is that elements represented as cells, for example elements owned, if selected in conjunction with a row or a column, in the event of an inverted axis, produces a mixed selection of all the elements in the model explorer. <br />
| + | |
| − | | + | |
| − | {{multiple image
| + | |
| − | | width = 350
| + | |
| − | | align = center
| + | |
| − | | direction = horizontal
| + | |
| − | | image1 = MixedSelection.png
| + | |
| − | | caption1 = MixedSelection
| + | |
| − | | image2 = MixedSelectionReq.png
| + | |
| − | | caption2 = MixedSelectionReq
| + | |
| − | }}
| + | |
| − | {{clear}} <br />
| + | |
| − | | + | |
| − | === From the model explorer ===
| + | |
| − | | + | |
| − | As a reminder, selections initiated by the model explorer will only result in column or row selections as the table has no means of knowing what type of selection is required by the user. <br />
| + | |
| − | | + | |
| − | | + | |
| − | == Styles in Papyrus' tables ==
| + | |
| − | | + | |
| − | It is important to note that the changes below are coming into eclipse Mars as they are dependant on a modification of the model. <br />
| + | |
| − | | + | |
| − | === Styles in the resize of a table's components ===
| + | |
| − | | + | |
| − | NamedStyles are used to introduce those changes and intValues ares used to mark the resizing of table elements. <br />
| + | |
| − | Below is the default model used for the table used to demonstrate the changes when styles are written and/or applied in a table. <br />
| + | |
| − | | + | |
| − | [[File:defaultTable.png|center|defaultTable|thumb|350px]] <br />
| + | |
| − | | + | |
| − | ==== Resize of the Headers ====
| + | |
| − | | + | |
| − | Sliding the header's cell frontier will result in the creation of a <I> localHeaderAxisConfiguration </I> and to it will be add the new values of the header's width and/or height. Both sets of headers can have stored values for heoght and width as the table can be inverted and if so the row and the column headers will be too. <br />
| + | |
| − | Below is the state of the model during the first change: resizing the row headers' index and label. <br />
| + | |
| − | | + | |
| − | In this case the local header created is the RowHeader but if the column headers are changed the model gets a ColumnHeader as illustrated by the image below. <br />
| + | |
| − | | + | |
| − | {{multiple image
| + | |
| − | | width = 350
| + | |
| − | | align = center
| + | |
| − | | direction = horizontal
| + | |
| − | | image1 = resizeRowHeaders.png
| + | |
| − | | caption1 = resizeRowHeaders
| + | |
| − | | image2 = resizeAllHeaders.png
| + | |
| − | | caption2 = resizeAllHeaders
| + | |
| − | }}
| + | |
| − | {{clear}} <br />
| + | |
| − | | + | |
| − | ==== Resize of the Axis ====
| + | |
| − | | + | |
| − | The values carried by the localHeaders only affect the headerLayer of the table and therefore the height or width of the Axis (columns and/or rows) will not be affected by them. For those to change, new values will be carried by the Axis themselves as can be seen in the following image. Of course, the method used to change the values is the same sliding of the frontier used when resizing the headers. <br />
| + | |
| − | | + | |
| − | [[File:resizeAxis.png|center|resizeAxis|thumb|350px]] <br />
| + | |
| − | | + | |
| − | In this example one row and two columns were changed and they all bear the corresponding value in their Axis element. <br /> <br />
| + | |
| − | | + | |
| − | === Styles in the merge of Axis elements ===
| + | |
| − | | + | |
| − | For this type of change the NamedStyles used are booleanValues, indicating if the Axis are to be merged or not. <br />
| + | |
| − | The behavior has been copied from the previous one and the booleans will be caried by the Axis, in case of a user selecting the axis to be merged, or the localHeaders if the user chooses to merge all the rows or columns of the table in one go. <br />
| + | |
| − | To initiate the merge, the user has access to a merge menu and chooses between the four types of merge the one best suited to the task (as illustrated below). The programm then proceeds to merge the cells of same value inside the selection. <br />
| + | |
| − | | + | |
| − | [[File:mergeOptions.png|center|mergeOptions|thumb|350px]] <br />
| + | |
| − | | + | |
| − | ==== Merge selected Axis ====
| + | |
| − | | + | |
| − | As mentionned above, in case of a merge of a selected axis, the boolean will be caried by the Axis element in the model. <br />
| + | |
| − | | + | |
| − | [[File:booleanMergeSelectedColumn.png|center|booleanMergeSelectedColumn|thumb|350px]] <br />
| + | |
| − | | + | |
| − | The other choices will then be greyed-out and a toggle will be displayed on the selected option to notify the user that this is (or these are) the axis merge. <br />
| + | |
| − | | + | |
| − | [[File:mergeSelectedColumns2.png|center|mergeSelectedColumns2|thumb|350px]] <br />
| + | |
| − | | + | |
| − | If the user selects a cell or an axis that has not been part of the previously merged selection, the toggle will not be displayed but the option will still be visible as the other will still be greyed-out. <br />
| + | |
| − | It is important to note that, if the user so chooses, the merge option can be reapplied to the new selection and the merge span will consist of the newly selected axis. A cautionary note however as only full rows or columns will be merged. <br />
| + | |
| − | | + | |
| − | {{multiple image
| + | |
| − | | width = 250
| + | |
| − | | align = center
| + | |
| − | | direction = horizontal
| + | |
| − | | image1 = mergeSelectedColumns.png
| + | |
| − | | caption1 = mergeSelectedColumns
| + | |
| − | | image2 = mergeSelectedRow.png
| + | |
| − | | caption2 = mergeSelectedRow
| + | |
| − | | image3 = mergeSelectedRows2.png
| + | |
| − | | caption3 = mergeSelectedRows2
| + | |
| − | | image4 = mergeSelectedRows3.png
| + | |
| − | | caption4 = mergeSelectedRows3
| + | |
| − | }}
| + | |
| − | {{clear}} <br />
| + | |
| − | | + | |
| − | ==== Merge All row/column Axis ====
| + | |
| − | | + | |
| − | The user can merge all the rows in the table and the result will look like this. <br />
| + | |
| − | | + | |
| − | {{multiple image
| + | |
| − | | width = 350
| + | |
| − | | align = center
| + | |
| − | | direction = horizontal
| + | |
| − | | image1 = booleanMergeAllRows.png
| + | |
| − | | caption1 = booleanMergeAllRows
| + | |
| − | | image2 = mergeAllRows2.png
| + | |
| − | | caption2 = mergeAllRows2
| + | |
| − | }}
| + | |
| − | {{clear}} <br />
| + | |
| − | | + | |
| − | == Edition of merged Cells ==
| + | |
| − | | + | |
| − | Once the cells are merged, the user might want to edit them. This edition can be problematic as the merge only takes into account the values of the cells and not their types when applying the merge option. This is shown in the example below asa classifier can be an activity but not the other way around. <br />
| + | |
| − | The first image illustrates the model and the profile's stereotype, applied on both classes, containing the three attributes activity and classifiers. <br />
| + | |
| − | | + | |
| − | [[File:tableProfileElements.png|center|tableProfileElements|thumb|350px]] <br />
| + | |
| − | | + | |
| − | When the user clicks on the left most part of the merged area, under the activity label, the editing tool only shows activity1 as a possible choice. But if the user selects the right side, under the classifier label, then the choices are many. In this example the choice is to apply the interface type to the merged cells and handle the editing behavior as illustrated by the three next images. <br />
| + | |
| − | | + | |
| − | {{multiple image
| + | |
| − | | width = 300
| + | |
| − | | align = center
| + | |
| − | | direction = horizontal
| + | |
| − | <!-- | footer = edition of the row cells -->
| + | |
| − | | image1 = activityEdition.png
| + | |
| − | | caption1 = activity edition
| + | |
| − | | image2 = classifierEdition.png
| + | |
| − | | caption2 = classifier edition
| + | |
| − | | image3 = editedTable.png
| + | |
| − | | caption3 = edition's result
| + | |
| − | }}
| + | |
| − | {{clear}} <br />
| + | |
| − | | + | |
| − | The tool will then automatically detect the possibility, or impossibility, of the edition and split the merge accordingly. <br />
| + | |
| − | Please note that the merge selection will not be changed and the selected axis will still carry their merge booleans as other values might still be equal and therefore the user might still want those merged. <br />
| + | |
