*Planed Commit the work based on ItemProviders: - that sort of implementation uses some EMF.edit commands like SetCommand, AddCommand or CreateChildCommand etc for manipulating the features of modelling elements with support for undo/redo - also, ItemProvider is an observer of the UML items (the notifiers), and provides for Eclipse framework a label, a property descriptor, etc and are supposed to be easy to use in a possible future version of an Eclipse GEF editor - study & search a method to implement the ModelEventPump
*Achieved - I found a generic ChangeCommand that can be used without all the ItemProvider hassle, so this would allow the implementation not be to Eclipse specific. I asked for support on the Eclipse UML 2 news forum and I got a confirmation that it's an alternative to use the ChangeCommand directly on the UML elements rather then ItemProviders with their commands (Set, Add, etc). This command stores the history of all changes to the model, and can undo and redo in it's history. - I implemented and committed a working implementation of the Association UML element using the ChangeCommand. - I started studying the ModelEventPump mechanism from ArgoUML and I sketched an implementation (this is needed to test the actual consequences of undo/redo of model changes to ArgoUML) *Problems I have trouble with the property names of the events which should be fired by the ModelEventPump (I'll send a separate message about these problems) *Plan for the next week - Solve the property names problems - Implement the ModelEventPumpEumlImpl - Test the undo/redo features with the ModelEventPump - Continue the adaptation of all other UML elements to use a ChangeCommand Bogdan, --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
