diff options
author | Stéphane Bégaudeau | 2016-05-24 14:44:58 +0000 |
---|---|---|
committer | Stéphane Bégaudeau | 2016-05-24 14:44:58 +0000 |
commit | 3896d7c12d6d3ba1884e72ca44b0d3c9f79b4bc7 (patch) | |
tree | b54992849e2b816beb2a32c5009d77404820c99a /doc | |
parent | bfff6e281e11217566d18a505b98484e6635bea7 (diff) | |
download | org.eclipse.eef-3896d7c12d6d3ba1884e72ca44b0d3c9f79b4bc7.tar.gz org.eclipse.eef-3896d7c12d6d3ba1884e72ca44b0d3c9f79b4bc7.tar.xz org.eclipse.eef-3896d7c12d6d3ba1884e72ca44b0d3c9f79b4bc7.zip |
Update the documentation for EEnum and radio buttons
Change-Id: Id64dbe496593bb8e39cb5467e4d4494aa2ab4357
Signed-off-by: Stéphane Bégaudeau <stephane.begaudeau@obeo.fr>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/org.eclipse.eef.documentation/pages/language/widgets/radio.html | 11 | ||||
-rw-r--r-- | doc/org.eclipse.eef.documentation/pages/language/widgets/radio.textile | 10 |
2 files changed, 10 insertions, 11 deletions
diff --git a/doc/org.eclipse.eef.documentation/pages/language/widgets/radio.html b/doc/org.eclipse.eef.documentation/pages/language/widgets/radio.html index bd3a67431..a273924b8 100644 --- a/doc/org.eclipse.eef.documentation/pages/language/widgets/radio.html +++ b/doc/org.eclipse.eef.documentation/pages/language/widgets/radio.html @@ -33,21 +33,20 @@ <code>aql:'Visibility:'</code> </li> <li>valueExpression: - <code>aql:self.visibility</code> + <code>aql:packagename::Visibility.getEEnumLiteral(self.visibility.toString())</code> </li> <li>editExpression: - <code>aql:self.eSet('visibility', newValue)</code> + <code>aql:self.eSet('visibility', newValue.instance)</code> </li> <li>candidatesExpression: - <code>aql:packagename::Visibility.eLiterals.generatedValue</code> + <code>aql:packagename::Visibility.eLiterals</code> </li> <li>candidateDisplayExpression: - <code>aql:candidate.getName()</code> + <code>aql:candidate.name</code> </li> </ul> <p>In this scenario, we will display a property with the eType «Visibility» coming from a package with the name «packagename». EEF does not provide a default interpreter but you can easily configure EEF to be used with the AQL interpreter. In the integration of EEF with the AQL interpreter, you can register additional services, written in Java, in which you can expose to AQL new operations. The operation - <code>eSet(java.lang.String, java.lang.Object)</code> used in the example does not exist in AQL. You would have to create it yourself. In a similar fashion, you would have to create the service - <code>getName()</code> on the EEnum generated value since it does not exist in AQL. + <code>eSet(java.lang.String, java.lang.Object)</code> used in the example does not exist in AQL. You would have to create it yourself. </p> </body> </html>
\ No newline at end of file diff --git a/doc/org.eclipse.eef.documentation/pages/language/widgets/radio.textile b/doc/org.eclipse.eef.documentation/pages/language/widgets/radio.textile index aa4f9154a..7a66ab290 100644 --- a/doc/org.eclipse.eef.documentation/pages/language/widgets/radio.textile +++ b/doc/org.eclipse.eef.documentation/pages/language/widgets/radio.textile @@ -17,9 +17,9 @@ h3(#displayeenum). Display an EEnum In order to display in the user interface some radio buttons with the value of an EAttribute with an eType EEnum (i.e. the visibility of an EObject), you can create a radio widget with the following properties: * labelExpression: @aql:'Visibility:'@ -* valueExpression: @aql:self.visibility@ -* editExpression: @aql:self.eSet('visibility', newValue)@ -* candidatesExpression: @aql:packagename::Visibility.eLiterals.generatedValue@ -* candidateDisplayExpression: @aql:candidate.getName()@ +* valueExpression: @aql:packagename::Visibility.getEEnumLiteral(self.visibility.toString())@ +* editExpression: @aql:self.eSet('visibility', newValue.instance)@ +* candidatesExpression: @aql:packagename::Visibility.eLiterals@ +* candidateDisplayExpression: @aql:candidate.name@ -In this scenario, we will display a property with the eType "Visibility" coming from a package with the name "packagename". EEF does not provide a default interpreter but you can easily configure EEF to be used with the AQL interpreter. In the integration of EEF with the AQL interpreter, you can register additional services, written in Java, in which you can expose to AQL new operations. The operation @eSet(java.lang.String, java.lang.Object)@ used in the example does not exist in AQL. You would have to create it yourself. In a similar fashion, you would have to create the service @getName()@ on the EEnum generated value since it does not exist in AQL.
\ No newline at end of file +In this scenario, we will display a property with the eType "Visibility" coming from a package with the name "packagename". EEF does not provide a default interpreter but you can easily configure EEF to be used with the AQL interpreter. In the integration of EEF with the AQL interpreter, you can register additional services, written in Java, in which you can expose to AQL new operations. The operation @eSet(java.lang.String, java.lang.Object)@ used in the example does not exist in AQL. You would have to create it yourself.
\ No newline at end of file |