|
| Re: How to 'associate' an ecore model to an viewpoint representation? [message #1262202 is a reply to message #1261477] |
Mon, 03 March 2014 11:15  |
|
Hi,
Le 02/03/2014 18:06, Wilhelm Pflüger a écrit :
> In the Sirius Specifier Manual / Specifying Viewpoints i found this
> sentence:
> "Auto-completion is available in these fields using the Ctrl+Space
> shortcut. It is recommended to explicitly associate a meta-model (or
> more) to your representations definitions to allow for smarter
> completion. Otherwise by default it will include all types from any EMF
> meta-model available."
>
> I'm not very familiar with neither Sirius nor eclipse in general and so
> i'm stuck on the problem how to 'associate' my meta-model to the
> representations definitions.
See Sirius Specifier Manual > Specifying Diagram Editors > Diagram
Description [1] or Sirius Specifier Manual > Specifying Table Editors >
Edition Tables [2] or Sirius Specifier Manual > Specifying Tree Editors
> Table Descriptions [3]:
It is recommended that the Diagram/Table/Tree Description be explicitly
associated with the meta-model(s) of the semantic elements it will
represent. You can add referenced meta-models from different sources in
the Metamodels property section of the Diagram/Table/Tree Description.
Sirius will work even without this association, but setting it
explicitly will give you better feedback when validating your VSM.
> Up to now my approach to get the meta-model into the focus of the
> representation design (and thus into code completion) is to generate
> code from the ecore model and to start an eclipse instance with this new
> generated component.
The best practice is to work with deployed meta-models and to use the
add from registry button to reference the meta-models (no change will be
needed for the deployment of the Viewpoint Specification Project) (See
[4] and [5]).
But I understood (misunderstood, maybe) that one
> can create a DSM designer without any code generation with sirius.
>
> Can someone clarify this?
The Viewpoint Specification Model (VSM, the .odesign file) contains your
representation and does not require any code generation (in opposite to
modelers designed with GFM Tooling for example): the description is
dynamically interpreted to materialize the workbench within the Eclipse
IDE. Sirius is supposed to work on a dynamic instance (a model based on
a ecore meta-model whose code has not been generated) but this a
degraded mode and it is not fully tested.
Regards,
Maxime
[1]
http://www.eclipse.org/sirius/doc/specifier/diagrams/Diagrams.html#diagram_description
[2]
http://www.eclipse.org/sirius/doc/specifier/tables/Tables.html#edition_tables
[3]
http://www.eclipse.org/sirius/doc/specifier/trees/Trees.html#tree_description
[4]
http://www.eclipse.org/sirius/doc/specifier/general/Specifying_Viewpoints.html#dynamic
[5]
http://www.eclipse.org/sirius/doc/specifier/general/Specifying_Viewpoints.html#vsp
Maxime Porhel - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
Powered by
FUDForum. Page generated in 0.02875 seconds
] 
Search
Help
Register
Login
Home
