diff options
3 files changed, 68 insertions, 62 deletions
diff --git a/plugins/org.eclipse.sirius.doc/doc/specifier/properties/Properties_View_Description.html b/plugins/org.eclipse.sirius.doc/doc/specifier/properties/Properties_View_Description.html index 6f75aafc6b..6b5c1b15f2 100644 --- a/plugins/org.eclipse.sirius.doc/doc/specifier/properties/Properties_View_Description.html +++ b/plugins/org.eclipse.sirius.doc/doc/specifier/properties/Properties_View_Description.html @@ -68,7 +68,7 @@ <a href="#list">List</a> </li> <li> - <a href="#custom">Basic Custom Widgets</a> + <a href="#basic_custom_widgets">Basic Custom Widgets</a> </li> <li> <a href="#advanced_custom_widgets">Advanced Custom Widgets</a> @@ -79,7 +79,7 @@ <a href="#dynamic_mappings">Dynamic Mappings</a> </li> <li> - <a href="#containers">Containers and Layout</a> + <a href="#containers_and_layout">Containers and Layout</a> </li> <li> <a href="#styling">Styling</a> @@ -652,7 +652,9 @@ <a href="#properties_view_description">above</a> to determine the semantic elements for which a widget should be created. </p> <p>Much like the other properties view elements, you can specify the widget’s - <em>Label Expression</em>":#label_expression, + <a href="#label_expression"> + <em>Label Expression</em> + </a>, <a href="#help_expression"> <em>Help Expression</em> </a>, @@ -753,8 +755,8 @@ <p>For buttons, you must define the <em>Button Label Expression</em> which is used to compute the label displayed on the button and should return a string. If the expression is not specified, the default value is the empty string. </p> - <h4 id="pushed_button">Button Push</h4> - <p>To define the behavior of the button when it is pushed, simply specify the behavior associated to the edition inside the + <h4 id="pushed_button">Behavior executed on click</h4> + <p>To define the behavior of the button when it is clicked, simply specify the behavior associated to the edition inside the <em>Begin</em> element using all the standard <a href="../general/Model_Operations.html">model operations</a>. The root operation is executed in the context of the semantic target element. </p> @@ -787,10 +789,10 @@ <em>Value Expression</em> using the variable <code>value</code> and it should return a string. If the expression is not specified, the default value is the empty string. </p> - <h4 id="label_actions">Label Actions</h4> + <h4 id="label_actions">Widget Actions</h4> <p>A <em>Label</em> can optionally define one or more - <em>Actions</em>, which are created as children element of the + <em>Widget Actions</em>, which are created as children element of the <em>Label</em> element ( <em>New > Widget Action</em>). Each action has a <em>Label Expression</em> and a behavior defined by @@ -843,7 +845,7 @@ <em>Value Expression</em> which is used to compute the checked/unchecked state of the checkbox and so should return a boolean (return <em>true</em> to display the checkbox checked). </p> - <h4 id="checkbox_change_value">Value Change</h4> + <h4 id="checkbox_change_value">Change value</h4> <p>To define the behavior of the checkbox when the user clicks on it, you simply specify the behavior associated to the edition inside the <em>Begin</em> element using all the standard <a href="../general/Model_Operations.html">model operations</a>. @@ -888,7 +890,7 @@ <em>Candidates Expression</em>. </li> </ul> - <h4 id="select_change_value">Value Change</h4> + <h4 id="select_change_value">Change value</h4> <p>To define the behavior of the <em>Select</em> when the user selects a different element, you simply specify the behavior associated to the edition inside the <em>Begin</em> element using all the standard @@ -932,7 +934,7 @@ <em>Candidates Expression</em>. </li> </ul> - <h4 id="radio_change_value">Value Change</h4> + <h4 id="radio_change_value">Change value</h4> <p>To define the behavior of the radio group when the selection changes, you simply specify the behavior associated to the edition inside the <em>Begin</em> element using all the standard <a href="../general/Model_Operations.html">model operations</a>. @@ -969,15 +971,15 @@ <em>Value Expression</em> using the variable named <code>value</code> and it should return a String. </p> - <h4 id="hyperlink_click_on_value">Click on Value</h4> + <h4 id="hyperlink_click_on_value">Behavior executed on click</h4> <p>To define the behavior of the hyperlink when it is clicked, you simply specify the behavior associated to the edition inside the <em>Begin</em> element using all the standard <a href="../general/Model_Operations.html">model operations</a>. </p> - <h4 id="hyperlink_actions">Additional Hyperlink Actions</h4> + <h4 id="hyperlink_actions">Widget Actions</h4> <p>A <em>Hyperlink</em> can optionally define one or more - <em>Actions</em>, which are created as children element of the + <em>Widget Actions</em>, which are created as children element of the <em>Hyperlink</em> element ( <em>New > Widget Action</em>). Each action has a <em>Label Expression</em> and a behavior defined by @@ -1066,7 +1068,7 @@ </p> <p>Depending on the parameters configuration the list widget will be represented thanks to a list and multiple buttons when <a href="#list_actions"> - <em>Action Widgets</em> + <em>Widget Actions</em> </a> are defined. </p> <p>The definition of a list follows the general rules described @@ -1081,24 +1083,23 @@ <em>Display Expression</em> which is used to compute the text displayed in the text field and should return a string. It is evaluated in the context of the semantic target element and has access to the variable <code>value</code> which corresponds to the element to display. </li> - <li>the " - <em>actions</em>"#actions are used to associate some buttons to the text field. + <li>the + <a href="#list_actions"> + <em>Widget Actions</em> + </a> are used to associate some buttons to the text field. </li> </ul> - <h4 id="list_click_on_value">Click on Value</h4> - <p>If the - <em>On Click Operation</em> is set then this operation defines the behavior executed when the user clicks or double-clicks on an element in the table. A variable named - <code>onClickEventKind</code> is available to determine if the operation has been triggered by a single click or double click. In case of a single click, the variable has the value “SINGLE_CLICK” and “DOUBLE_CLICK” in case of a double click. - </p> + <h4 id="list_on_click_operation">Behavior executed on click</h4> <p>To define the behavior, you simply specify the behavior associated to the edition inside the <em>Begin</em> element using all the standard - <a href="../general/Model_Operations.html">model operations</a>. + <a href="../general/Model_Operations.html">model operations</a>. A variable named + <code>onClickEventKind</code> is available to determine if the operation has been triggered by a single click or double click. In case of a single click, the variable has the value “SINGLE_CLICK” and “DOUBLE_CLICK” in case of a double click. </p> <p>The expressions defined under the <em>Begin</em> can use the <code>selection</code> variable which represents the values selected by the user. This variable will contain the list of the values selected. </p> - <h4 id="list_actions">Actions</h4> + <h4 id="list_actions">Widget actions</h4> <p>A list can contain <em>actions</em> which represent <strong>buttons</strong> associated to the list field. @@ -1123,7 +1124,7 @@ <a href="#conditional_styles">conditional styles</a> and <a href="#widgets_styles">widgets styles</a> section to find details on what is specific to widgets. </p> - <h3 id="custom">Basic Custom Widgets</h3> + <h3 id="basic_custom_widgets">Basic Custom Widgets</h3> <p>A <em>Custom Description</em> is used when none of the predefined styles correspond to your need. Custom widgets are implemented in Java and use the <code>org.eclipse.eef.ide.ui.eefLifecycleManagerProvider</code> extension point. @@ -1137,12 +1138,12 @@ <p>See <a href="../../developer/extensions-properties_provide_custom_widget_basic.html">the reference documentation</a> for how to actually implement your own basic custom widgets. </p> - <h5 id="custom_expression">Custom Expression/Operation</h5> + <h5 id="basic_custom_widgets_expression">Custom Expression/Operation</h5> <p>When you define a custom widget, it is possible to define some custom expression or operation which will be used by the custom widget implementation. <br/>In this case, the <em>Identifier</em> is mandatory. It would be used in the Java code to find the expression/operation contributed with the VSM. </p> - <h5 id="custom_styles">Custom Styles</h5> + <h5 id="basic_custom_widgets_styles">Custom Styles</h5> <p>See the <a href="#styling">styles</a> section for a general presentation of how styles are defined, including <a href="#conditional_styles">conditional styles</a> and @@ -1218,7 +1219,7 @@ <p>Thanks to this mechanism we defined that all the <code>String</code> elements in our metamodel will be represented with a text field. </p> - <h2 id="containers">Containers and Layout</h2> + <h2 id="containers_and_layout">Containers and Layout</h2> <p>Sirius provides a default algorithm to perform an automatic layout of all the controls in a properties view. If the default algorithm does not fit your needs, you can specify some parameters for alternate layouts directly inside the VSM. To do this you must first create a <em>Container</em> which will contains all the widgets to which the layout will apply, and then create and configure the layout to be used by the container to organize its children widgets: </p> diff --git a/plugins/org.eclipse.sirius.doc/doc/specifier/properties/Properties_View_Description.textile b/plugins/org.eclipse.sirius.doc/doc/specifier/properties/Properties_View_Description.textile index 7a36bf29d2..ca55b4199d 100644 --- a/plugins/org.eclipse.sirius.doc/doc/specifier/properties/Properties_View_Description.textile +++ b/plugins/org.eclipse.sirius.doc/doc/specifier/properties/Properties_View_Description.textile @@ -178,7 +178,7 @@ A widget is used to represent model elements in the properties view and, for mos The definition of a widget follows the general rules described "above":#properties_view_description to determine the semantic elements for which a widget should be created. -Much like the other properties view elements, you can specify the widget's _Label Expression_":#label_expression, "_Help Expression_":#help_expression, "_Is Enabled Expression_":#is_enabled_expression, "_Styles_":#styles, "_Conditional Styles_":#conditional_styles. +Much like the other properties view elements, you can specify the widget's "_Label Expression_":#label_expression, "_Help Expression_":#help_expression, "_Is Enabled Expression_":#is_enabled_expression, "_Styles_":#styles, "_Conditional Styles_":#conditional_styles. h3(#text). Text / Text area @@ -229,9 +229,9 @@ The definition of a button follows the general rules described "above":#widgets For buttons, you must define the _Button Label Expression_ which is used to compute the label displayed on the button and should return a string. If the expression is not specified, the default value is the empty string. -h4(#pushed_button). Button Push +h4(#pushed_button). Behavior executed on click -To define the behavior of the button when it is pushed, simply specify the behavior associated to the edition inside the _Begin_ element using all the standard "model operations":../general/Model_Operations.html. The root operation is executed in the context of the semantic target element. +To define the behavior of the button when it is clicked, simply specify the behavior associated to the edition inside the _Begin_ element using all the standard "model operations":../general/Model_Operations.html. The root operation is executed in the context of the semantic target element. h4(#button_styles). Button Styles @@ -249,9 +249,9 @@ The definition of a label follows the general rules described "above":#widgets t For labels, you must define the _Value Expression_ which is used to compute the text displayed in the description. The _Value Expression_ can return any kind of object but the result displayed will be the result of a call to @Object.toString()@. If you want to customize how the result will be displayed, you can return a string in the value expression or use the _Display Expression_. The _Display Expression_ will have access to the result of the _Value Expression_ using the variable @value@ and it should return a string. If the expression is not specified, the default value is the empty string. -h4(#label_actions). Label Actions +h4(#label_actions). Widget Actions -A _Label_ can optionally define one or more _Actions_, which are created as children element of the _Label_ element (_New > Widget Action_). Each action has a _Label Expression_ and a behavior defined by "model operations":../general/Model_Operations.html contained inside. If present, actions will be rendered as buttons on the right of the label itself. The button's text is defined by the _Label Expression_, and its behavior when pushed by the model operations. +A _Label_ can optionally define one or more _Widget Actions_, which are created as children element of the _Label_ element (_New > Widget Action_). Each action has a _Label Expression_ and a behavior defined by "model operations":../general/Model_Operations.html contained inside. If present, actions will be rendered as buttons on the right of the label itself. The button's text is defined by the _Label Expression_, and its behavior when pushed by the model operations. h4(#label_styles). Label Styles @@ -276,7 +276,7 @@ The definition of a checkbox follows the general rules described "above":#widget For checkboxes, you must define the _Value Expression_ which is used to compute the checked/unchecked state of the checkbox and so should return a boolean (return _true_ to display the checkbox checked). -h4(#checkbox_change_value). Value Change +h4(#checkbox_change_value). Change value To define the behavior of the checkbox when the user clicks on it, you simply specify the behavior associated to the edition inside the _Begin_ element using all the standard "model operations":../general/Model_Operations.html. @@ -299,7 +299,7 @@ For selects, you must define : * the _Candidate Display Expression_ which is used to compute the label displayed for each possible candidate in the combo and so should return a string. The _Candidate Display Expression_ can use the @candidate@ variable which represents the element currently evaluated. * the _Value Expression_ which is used to compute the element selected in the combo and should return an object, which should be an element of the collection returned by _Candidates Expression_. -h4(#select_change_value). Value Change +h4(#select_change_value). Change value To define the behavior of the _Select_ when the user selects a different element, you simply specify the behavior associated to the edition inside the _Begin_ element using all the standard "model operations":../general/Model_Operations.html. @@ -322,7 +322,7 @@ For radio groups, you must define : * the _Candidate Display Expression_ which is used to compute the label displayed for each possible candidate in the radio group and so should return a string. The _Candidate Display Expression_ can use the @candidate@ variable which represents the element currently evaluated. * the _Value Expression_ which is used to compute the element selected in the radio group and should return an object, which should be an element of the collection returned by _Candidates Expression_. -h4(#radio_change_value). Value Change +h4(#radio_change_value). Change value To define the behavior of the radio group when the selection changes, you simply specify the behavior associated to the edition inside the _Begin_ element using all the standard "model operations":../general/Model_Operations.html. @@ -342,13 +342,13 @@ The definition of an hyperlink follows the general rules described "above":#widg For hyperlinks, you must define the _Value Expression_ which is used to compute the hyperlink displayed. The _Value Expression_ can return any kind of object but the result displayed will be the result of a call to _java.lang.Object#toString()_. If you want to customize how the result will be displayed, you can return a String in the value expression or use the _Display Expression_. The _Display Expression_ will have access to the result of the _Value Expression_ using the variable named @value@ and it should return a String. -h4(#hyperlink_click_on_value). Click on Value +h4(#hyperlink_click_on_value). Behavior executed on click To define the behavior of the hyperlink when it is clicked, you simply specify the behavior associated to the edition inside the _Begin_ element using all the standard "model operations":../general/Model_Operations.html. -h4(#hyperlink_actions). Additional Hyperlink Actions +h4(#hyperlink_actions). Widget Actions -A _Hyperlink_ can optionally define one or more _Actions_, which are created as children element of the _Hyperlink_ element (_New > Widget Action_). Each action has a _Label Expression_ and a behavior defined by "model operations":../general/Model_Operations.html contained inside. If present, actions will be rendered as buttons on the right of the label itself. The button's text is defined by the _Label Expression_, and its behavior when pushed by the model operations. +A _Hyperlink_ can optionally define one or more _Widget Actions_, which are created as children element of the _Hyperlink_ element (_New > Widget Action_). Each action has a _Label Expression_ and a behavior defined by "model operations":../general/Model_Operations.html contained inside. If present, actions will be rendered as buttons on the right of the label itself. The button's text is defined by the _Label Expression_, and its behavior when pushed by the model operations. h4(#hyperlink_styles). Hyperlink Styles @@ -389,24 +389,22 @@ h3(#list). List A _List_ is used to represent a *list with buttons* in a "group":#groups or in a "container":#containers. -Depending on the parameters configuration the list widget will be represented thanks to a list and multiple buttons when "_Action Widgets_":#list_actions are defined. +Depending on the parameters configuration the list widget will be represented thanks to a list and multiple buttons when "_Widget Actions_":#list_actions are defined. The definition of a list follows the general rules described "above":#widgets to determine the semantic elements for which a list should be created. It is evaluated in the context of the semantic target element. For lists, you must define: * the _Value Expression_ which is used to compute the element to display and should return an object. * the _Display Expression_ which is used to compute the text displayed in the text field and should return a string. It is evaluated in the context of the semantic target element and has access to the variable @value@ which corresponds to the element to display. -* the "_actions_"#actions are used to associate some buttons to the text field. +* the "_Widget Actions_":#list_actions are used to associate some buttons to the text field. -h4(#list_click_on_value). Click on Value +h4(#list_on_click_operation). Behavior executed on click -If the _On Click Operation_ is set then this operation defines the behavior executed when the user clicks or double-clicks on an element in the table. A variable named @onClickEventKind@ is available to determine if the operation has been triggered by a single click or double click. In case of a single click, the variable has the value "SINGLE_CLICK" and "DOUBLE_CLICK" in case of a double click. - -To define the behavior, you simply specify the behavior associated to the edition inside the _Begin_ element using all the standard "model operations":../general/Model_Operations.html. +To define the behavior, you simply specify the behavior associated to the edition inside the _Begin_ element using all the standard "model operations":../general/Model_Operations.html. A variable named @onClickEventKind@ is available to determine if the operation has been triggered by a single click or double click. In case of a single click, the variable has the value "SINGLE_CLICK" and "DOUBLE_CLICK" in case of a double click. The expressions defined under the _Begin_ can use the @selection@ variable which represents the values selected by the user. This variable will contain the list of the values selected. -h4(#list_actions). Actions +h4(#list_actions). Widget actions A list can contain _actions_ which represent *buttons* associated to the list field. @@ -422,7 +420,7 @@ h4(#list_styles). List Styles See the "styles":#styling section for a general presentation of how styles are defined, including "conditional styles":#conditional_styles and "widgets styles":#widgets_styles section to find details on what is specific to widgets. -h3(#custom). Basic Custom Widgets +h3(#basic_custom_widgets). Basic Custom Widgets A _Custom Description_ is used when none of the predefined styles correspond to your need. Custom widgets are implemented in Java and use the @org.eclipse.eef.ide.ui.eefLifecycleManagerProvider@ extension point. @@ -432,12 +430,12 @@ For custom widgets, the _Identifier_ is mandatory. It is used to find the widget See "the reference documentation":../../developer/extensions-properties_provide_custom_widget_basic.html for how to actually implement your own basic custom widgets. -h5(#custom_expression). Custom Expression/Operation +h5(#basic_custom_widgets_expression). Custom Expression/Operation When you define a custom widget, it is possible to define some custom expression or operation which will be used by the custom widget implementation. In this case, the _Identifier_ is mandatory. It would be used in the Java code to find the expression/operation contributed with the VSM. -h5(#custom_styles). Custom Styles +h5(#basic_custom_widgets_styles). Custom Styles See the "styles":#styling section for a general presentation of how styles are defined, including "conditional styles":#conditional_styles and "widgets styles":#widgets_styles section to find details on what is specific to widgets. This section only presents the aspects which are specific to texts. @@ -468,7 +466,7 @@ If we take one of the default rules implemented by Sirius we have: Thanks to this mechanism we defined that all the @String@ elements in our metamodel will be represented with a text field. -h2(#containers). Containers and Layout +h2(#containers_and_layout). Containers and Layout Sirius provides a default algorithm to perform an automatic layout of all the controls in a properties view. If the default algorithm does not fit your needs, you can specify some parameters for alternate layouts directly inside the VSM. To do this you must first create a _Container_ which will contains all the widgets to which the layout will apply, and then create and configure the layout to be used by the container to organize its children widgets: diff --git a/plugins/org.eclipse.sirius.doc/doc/toc.xml b/plugins/org.eclipse.sirius.doc/doc/toc.xml index ab89dce06c..4cb86ba5dd 100644 --- a/plugins/org.eclipse.sirius.doc/doc/toc.xml +++ b/plugins/org.eclipse.sirius.doc/doc/toc.xml @@ -119,17 +119,17 @@ <topic href="doc/specifier/properties/Properties_View_Description.html#groups" label="Groups"> <topic href="doc/specifier/properties/Properties_View_Description.html#group_styles" label="Group styles"></topic> </topic> - <topic href="doc/specifier/properties/Properties_View_Description.html#controls" label="Controls"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#widgets" label="Widgets"> <topic href="doc/specifier/properties/Properties_View_Description.html#text" label="Text / Text area"> - <topic href="doc/specifier/properties/Properties_View_Description.html#edit_text" label="Edit text"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#edit_text" label="Text edition"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#text_styles" label="Text/Text area styles"></topic> </topic> <topic href="doc/specifier/properties/Properties_View_Description.html#button" label="Button"> - <topic href="doc/specifier/properties/Properties_View_Description.html#pushed_button" label="Pushed button"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#pushed_button" label="Behavior executed on click"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#button_styles" label="Button styles"></topic> </topic> <topic href="doc/specifier/properties/Properties_View_Description.html#label" label="Label"> + <topic href="doc/specifier/properties/Properties_View_Description.html#label_actions" label="Widget actions"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#label_styles" label="Label styles"></topic> </topic> <topic href="doc/specifier/properties/Properties_View_Description.html#checkbox" label="Checkbox"> @@ -145,36 +145,43 @@ <topic href="doc/specifier/properties/Properties_View_Description.html#radio_styles" label="Radio styles"></topic> </topic> <topic href="doc/specifier/properties/Properties_View_Description.html#hyperlink" label="Hyperlink"> - <topic href="doc/specifier/properties/Properties_View_Description.html#hyperlink_click_on_value" label="Click on value"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#hyperlink_click_on_value" label="Behavior executed on click"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#hyperlink_actions" label="Widget actions"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#hyperlink_styles" label="Hyperlink styles"></topic> </topic> <topic href="doc/specifier/properties/Properties_View_Description.html#reference" label="Reference"> - <topic href="doc/specifier/properties/Properties_View_Description.html#reference_click_on_value" label="Click on value"></topic> - <topic href="doc/specifier/properties/Properties_View_Description.html#actions" label="Actions"></topic> - <topic href="doc/specifier/properties/Properties_View_Description.html#action_pushed_button" label="Action pushed button"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#reference_styles" label="Reference styles"></topic> </topic> - <topic href="doc/specifier/properties/Properties_View_Description.html#custom" label="Custom"> - <topic href="doc/specifier/properties/Properties_View_Description.html#custom_expression" label="Custom Expression/Operation"></topic> - <topic href="doc/specifier/properties/Properties_View_Description.html#custom_styles" label="Custom styles"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#list" label="List"> + <topic href="doc/specifier/properties/Properties_View_Description.html#list_on_click_operation" label="Behavior executed on click"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#list_actions" label="Widget actions"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#list_action_pushed_button" label="Action pushed button"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#list_styles" label="List styles"></topic> </topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#basic_custom_widgets" label="Basic custom widgets"> + <topic href="doc/specifier/properties/Properties_View_Description.html#basic_custom_widgets_expression" label="Custom Expression/Operation"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#basic_custom_widgets_styles" label="Custom styles"></topic> + </topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#advanced_custom_widgets" label="Advanced custom widgets"></topic> </topic> <topic href="doc/specifier/properties/Properties_View_Description.html#dynamic_mappings" label="Dynamic mappings"></topic> - <topic href="doc/specifier/properties/Properties_View_Description.html#containers" label="Containers"> - <topic href="doc/specifier/properties/Properties_View_Description.html#layout" label="Layout"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#containers_and_layout" label="Containers and Layout"> </topic> </topic> <topic href="doc/specifier/properties/Properties_View_Description.html#styling" label="Styling"> <topic href="doc/specifier/properties/Properties_View_Description.html#widgets_styles" label="Widgets styles"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#colors" label="Colors"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#conditional_styles" label="Conditional styles"></topic> - <topic href="doc/specifier/properties/Properties_View_Description.html#label_properties" label="Label properties"></topic> </topic> <topic href="doc/specifier/properties/Properties_View_Description.html#validation_rules" label="Validation rules"> <topic href="doc/specifier/properties/Properties_View_Description.html#page_semantic_validation_rule" label="Page semantic validation rule"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#group_semantic_validation_rule" label="Group semantic validation rule"></topic> <topic href="doc/specifier/properties/Properties_View_Description.html#group_property_validation_rule" label="Group property validation rule"></topic> </topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#extension_points" label="Extension Points"> + <topic href="doc/specifier/properties/Properties_View_Description.html#advanced_custom_widgets_extension_points" label="Extension Points for Advanced Custom Widgets"></topic> + <topic href="doc/specifier/properties/Properties_View_Description.html#tab_filtering" label="Tab Filtering"></topic> + </topic> </topic> <anchor id="moreSpecifierDialectRefs" /> <topic href="doc/specifier/general/ToolsSpecification.html" label="Tools Specification" /> |