Home » Eclipse Projects » Sirius » GSOC2014 - Specification model initializer(Some questions)
|
| Re: GSOC2014 - Specification model initializer [message #1386802 is a reply to message #1386761] |
Fri, 20 June 2014 15:12   |
|
Hi João
Le 20/06/2014 10:03, João Martins a écrit :
> Hi, I was working on bugs 434695 and 436332 with a branch gsoc2014 on
> repo. Now I want to start the project and do a good job on it.
> I have some question about it:
>
> -when I start search what I should do I think I would create a all new
> plugin with a new project, but I start to search on repo and now I think
> I will create a new template on a existing project and specific package
> like gouping action.
You will commit on the gsoc2014 branch, so I think you could create some
new packages for the initializer code but it will be better to add the
code in a separated plugin project.
So you can create some new projects in your gsoc2014 branch. If you add
initialization helpers for the diagram dialect, you can add them in a
org.eclipse.sirius.editor.diagram.initializer plugin, and in
org.eclipse.sirius.editor.table.initializer for the table dialect.
>
> -I don't have sure what I should do but I think I need to create a
> template of VMS (.ecore), when the user want to create a new VSM he
> should have options to choose some tool to have initialized.
Regarding our current discussions about actions, menus and wizards, you
do not have to modify Sirius ecore files.
But be aware that a notion of RepresentationTemplate exists in the
metamodel and has been used to define a Sequence Diagram Template. It
could be a different way to imagie the initializer, as the specifier
would create a set of elements in the VSM, and a concrete
DiagramDescription would be generated. This way is much more
complicated: it would require a new ecore model, extending diagram.ecore
and a set of transformation rule to create a DiagramDescription from a
template. Furthermore it would not lead to a result before the end of
the GSOC.
>
> -In Sirius project it have some package/class with similar code where
> I can understand how to do this part of project?
If you add menu/actions/wizard in the VSM editor, you can look into the
org.eclipse.sirius.editor.tools.api.menu.AbstractMenuBuilder
implementations and in the code area you used in bugs 434695 and 436332 .
>
>
> Best regards João Martins
Regards,
Maxime
Maxime Porhel - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
| Re: GSOC2014 - Specification model initializer [message #1386956 is a reply to message #1386802] |
Mon, 23 June 2014 08:59 |
 João Martins
Messages: 11
Registered: May 2014 |
Junior Member |
|
|
Tanks for the answer Maxime,
The Initializer the user will have the possibility to create any EObject of Sirius,
Example 1:
Right click on "Viewpoint" and we have the option of "Initialize", when we click it can show a PopUp where the user can select if want one or more Objects created, I want to say with this, he can create tools from "New Extension", "New Import", "New Representation", "New Template" or/and "New Validation".
Example 2:
(Using the info of the previous example)
If the user want to create for examples 5 Diagram Description, in PopUp, the user
can select many tools as he want to add, having a list of the tools added and the tools
he can add, for this case only show the tools that can only be initialized in "ViewPoint"
Best Regards
João Martins
|
|
|
| Re: GSOC2014 - Specification model initializer [message #1387068 is a reply to message #1386956] |
Mon, 23 June 2014 20:46 |
|
Le 23/06/2014 10:59, João Martins a écrit :
> Tanks for the answer Maxime,
>
> The Initializer the user will have the possibility to create any EObject of Sirius,
>
> Example 1:
> Right click on "Viewpoint" and we have the option of "Initialize", when we click it can show a PopUp where the user can select if want one or more Objects created, I want to say with this, he can create tools from "New Extension", "New Import", "New Representation", "New Template" or/and "New Validation".
The initializer actions/wizard must not just propose the same element
creations than the right clic menus New... .
The initializer should facilitate the creation of some standard diagram
description. For example, if the user selected a "Class Diagram" pattern
(proposed by a wizard, and with maybe some little configuration a a
wizard page), the initializer could create a squeleton of a class
diagram (several mappings (container, node, edge, already linked
together, with default styles), with some created tools (creation,
direct edit, delete, for example).
Then the specifier has just to enter some expression and domain class,
and complete the tools.
>
> Example 2:
> (Using the info of the previous example)
> If the user want to create for examples 5 Diagram Description, in PopUp, the user
> can select many tools as he want to add, having a list of the tools added and the tools
> he can add, for this case only show the tools that can only be initialized in "ViewPoint
You proposed something redundant with the already existing new child menus.
The goal of this part of the GSOC is to help the user with the creation
of some patterns/squeletons of VSM created in one clic.
>
> Best Regards
> João Martins
>
Regards,
Maxime
Maxime Porhel - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
Goto Forum:
Current Time: Wed Sep 25 11:11:56 GMT 2024
Powered by FUDForum. Page generated in 0.03660 seconds |
] 
Search
Help
Register
Login
Home
