Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rwxr-xr-xplugins/doc/org.eclipse.papyrus.uml.textedit.doc/site/mediawiki/textedit.mediawiki34
1 files changed, 17 insertions, 17 deletions
diff --git a/plugins/doc/org.eclipse.papyrus.uml.textedit.doc/site/mediawiki/textedit.mediawiki b/plugins/doc/org.eclipse.papyrus.uml.textedit.doc/site/mediawiki/textedit.mediawiki
index 339bd151b6c..760b6841455 100755
--- a/plugins/doc/org.eclipse.papyrus.uml.textedit.doc/site/mediawiki/textedit.mediawiki
+++ b/plugins/doc/org.eclipse.papyrus.uml.textedit.doc/site/mediawiki/textedit.mediawiki
@@ -14,7 +14,7 @@ The default grammar of the XText parser for the Value Specification is the follo
<code><nowiki>(visibility)? (name'=')? value</nowiki></code>
The values accepted for the differents attributes are the following:
-{| class="wikitable"
+{| class="wikitable" border="1" cellspacing="0"
! style="width:20%" | Attribute
! style="width:10%" | Required
! style="width:60%" | Values accepted
@@ -61,7 +61,7 @@ The XText parser reacts differently instead of the type of the Value Specificati
If the type of Value Specification's container is not defined, the default behaviour will be applied.
Here, some examples:
-{| class="wikitable"
+{| class="wikitable" border="1" cellspacing="0"
! style="width:15%" rowspan="2" | Text filled
! style="width:20%" rowspan="2" | Namely
! style="width:65%" rowspan="1" colspan="4" | Created ValueSpecification
@@ -139,7 +139,7 @@ Here, some examples:
If the type of Value Specification's container is setted, the same text filled will be have different behaviour depending to the type. In fact, the value filled must be consistent to the type, otherwise an <code>OpaqueExpression</code> will be created.
The different types corresponding to <code>LiteralSpecification</code> are the following:
-{| class="wikitable"
+{| class="wikitable" border="1" cellspacing="0"
! style="width:50%" | LiteralSpecification
! style="width:50%" | Types corresponding
|-
@@ -183,7 +183,7 @@ The different types corresponding to <code>LiteralSpecification</code> are the f
|}
Here, some examples:
-{| class="wikitable"
+{| class="wikitable" border="1" cellspacing="0"
! style="width:15%" rowspan="2" | Text filled
! style="width:20%" rowspan="2" | Value Specification's container type
! style="width:65%" rowspan="1" colspan="4" | Created ValueSpecification
@@ -271,41 +271,41 @@ Here, some examples:
|}
==Textual Editor For Named Element==
-Since Papyrus 1.1.0 (Eclipse Mars), Papyrus provides a new texutal editor to edit references to UML NamedElement. This editor works only for references which are not in containment. This editor has not been developed using XText. It use a custom string parser and provide a completion (STRL+SPACE) to help the user to find the named elements to reference in the model.
+Since Papyrus 1.1.0 (Eclipse Mars), Papyrus provides a new texutal editor to edit references to UML NamedElement. This editor works only for references which are not in containment. This editor has not been developed using XText. It use a custom string parser and provide a completion (CTRL+SPACE) to help the user to find the named elements to reference in the model.
You can use this editor in Property View or in Papyrus table for example.
Developer documentation is available [[Papyrus_Developer_Guide/Papyrus_Embedded_Editors_Documentation/Textual_Editor_For_NamedElement|here]].
===Usage===
* This editors allows to find named element typing its name.
-* In case of several elements to found, the separator to use is the comma <code>'</code>
+* In case of several elements to found, the separator to use is the comma </code>'</code>
* If the name of the element contains a comma, you should prefix and suffix its name by a quote <code>'</code>.
* The value will not be set if the element can't be found is the model
===Example===
If you have 3 Classes in your model, named <code>Class1</code>, <code>Class2</code> and <code>Clas,s3</code>.
-{| class="wikitable"
+{| class="wikitable" border="1" cellspacing="0"
! style="font-weight: bold;" | typed text
! style="font-weight: bold;" | completion proposal
! style="font-weight: bold;" | explanation
|-
| empty string
-| null, ...
-| we look for nothing, so we provide the <code>null</code> value and <code>...</code> to ask to the user to write more text
+| <Undefined>, ...
+| we look for nothing, so we provide the <code><Undefined></code> value and <code>...</code> to ask to the user to write more text
|-
| Clas
-| null,Class1,Class2,Clas,s3
-| 3 classes matches the string, <code>null</code> is always proposed
+| <Undefined>,Class1,Class2,Clas,s3
+| 3 classes matches the string, <code><Undefined></code> is always proposed
|-
| Class
-| null,Class1,Class2
-| 3 classes matches the string, null is always proposed
+| <Undefined>,Class1,Class2
+| 3 classes matches the string, <Undefined>is always proposed
|-
| 'Clas
-| null, Clas,s3
-| the string starts with a quote and Clas,s3 contains a comma, so we propose <code>Clas,s3</code>; <code>null</code> is always proposed
+| <Undefined>, Clas,s3
+| the string starts with a quote and Clas,s3 contains a comma, so we propose <code>Clas,s3</code>; <code><Undefined></code> is always proposed
|-
| Clas,
-| null,...
-| interpreted as a list of value, the first value is <code>Clas</code>, and we have no information for the second one, for the completion it is an empty string
+| <Undefined>,...
+| interpreted as a list of value, the first value is </code>Clas</code>, and we have no information for the second one, for the completion it is an empty string
|}

Back to the top