Hello,

Sorry for the late reports. In week 5 didn't worked much because I
left Iasi (university town) to go in Mangalia (my home town) where
i'll stay for the summer.

Achieved:
- I spent quite a lot of time figuring out the way in which the model
subsystem implementation should use an EditiingDomain (which tracks
changes to the model, and so it can support undo and redo).

I presumed the UML model subsystem could have multiple instances (one
for each editor - in the future would be desirable to have multiple
editors in the same application). So it will be a 1-1 relationship
between an eUML instance and an editing domain.
Multiple instances of eUML will have their own EditingDomain, so every
eUML could have an independent undo/redo stack.

There is a problem with the current Model.initialise(String)
initialization and Model.setImplementation(ModelImplementation). In
the current form it only allows one implementation of Model to be used
as the Model. IMHO one should have the possibility to create multiple
instances (how many it needs) of the implementation of the Model
(maybe to support multiple editors in the same application).

I debugged the ArgoUML application to see how a model element is
created and used. I saw that when the user clicks, on mouse press
event the element is created (without an owner), and then on mouse
released event the owner is set.
Why isn't the owner set also when the element is created?

The eUML should be able to find out if it's inside an Eclipse plugin
or in a stand alone application. In the case of a standalone
application eUML should somehow know the location in the filesystem of
the "org.eclipse.uml2.uml.resource" jar plugin. So I thought that a
system property (System.getProperty(String key)) would be appropriate
to define the path of the jar. So if this property is defined then
it's the case of a standalone application, else it's an Eclipse
plugin.

To do next:
- continue the current implementation of the EditingDomain and submit
the code ASAP
- figure out the singleton pieces of the eUML implementation in the
case of multiple eUML instances

Problems:
I had some trouble understanding the relations between some classes in
org.eclipse.uml2.common.edit.command and EMF commands and how actually
they are used in conjunction with a model through implementation of
EditingDomain (AdapterFactoryEditingDomain), and some other few
classes. All the trouble had the cause that the classes have no
javadoc.

Bogdan,

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to