| Basics for creating a graphical UML editor [message #182169] |
Mon, 23 May 2005 04:23  |
Eclipse User |
|
|
|
Originally posted by: j.vanijperen.emaxx.nl
Hello,
For a project I've been asked to create a graphical editor in which
software can be designed. I want to make this design proces follow a
few of the UML diagrams.
I think I have an idea now on how this should be done, but I would like
some confirmation if this is a good approach, before I actually start making
this.
1. The base for all this, is a model. This model is the meta-model for the
"program model" people want to make. My model consists of some
classes (such as Diagram, Package, Class, Operation, etc). I want to
design this with the Omondo EclipseUML.
2. After I have my (meta)model, I make the Commands that can alter a
"program model".. (An instance of a model)
3. After that I make EditParts for it, to use in my GEF views. The EditParts
will listen to Notification messages from the model elements they represent.
4. After that I make the Figures that represent the EditParts on the canvas.
These will be controlled by the refreshVisuals() method in the EditParts.
5. Then I create my EditPolicies for my EditParts, which will take Requests
from the graphical interface and use them to return Commands (see 2).
Ofcourse, most of these things are part of an EditDomain, which also
contains other things, but this should be the basics... Right?
Thank you in advance.
Sincerely,
Jeroen v. IJperen
|
|
|
| Re: Basics for creating a graphical UML editor [message #182205 is a reply to message #182169] |
Mon, 23 May 2005 11:39  |
| Eclipse User |
|
|
|
Yes. And don't forget the EditPartFactory that would create new EditParts
given a model.
"Jeroen van IJperen" <j.vanijperen@emaxx.nl> wrote in message
news:429192EA.2EE66786@emaxx.nl...
> Hello,
>
> For a project I've been asked to create a graphical editor in which
> software can be designed. I want to make this design proces follow a
> few of the UML diagrams.
> I think I have an idea now on how this should be done, but I would like
> some confirmation if this is a good approach, before I actually start
making
> this.
>
> 1. The base for all this, is a model. This model is the meta-model for the
> "program model" people want to make. My model consists of some
> classes (such as Diagram, Package, Class, Operation, etc). I want to
> design this with the Omondo EclipseUML.
>
> 2. After I have my (meta)model, I make the Commands that can alter a
> "program model".. (An instance of a model)
>
> 3. After that I make EditParts for it, to use in my GEF views. The
EditParts
> will listen to Notification messages from the model elements they
represent.
>
> 4. After that I make the Figures that represent the EditParts on the
canvas.
> These will be controlled by the refreshVisuals() method in the EditParts.
>
> 5. Then I create my EditPolicies for my EditParts, which will take
Requests
> from the graphical interface and use them to return Commands (see 2).
>
> Ofcourse, most of these things are part of an EditDomain, which also
> contains other things, but this should be the basics... Right?
>
> Thank you in advance.
>
> Sincerely,
>
> Jeroen v. IJperen
>
|
|
|
Powered by
FUDForum. Page generated in 0.03273 seconds
Home