Here are some thoughts of areas I _may_ tackle after the next release. I'm also willing to help out with http://argouml.tigris.org/issues/show_bug.cgi?id=3497 where I can.
Obviously I'll be visiting our bugs list too on the way. Shrink PGML save ============== http://argouml.tigris.org/issues/show_bug.cgi?id=4307 A very small job that I'll definitely do. My early experiments with this cut my projects down by a third. Some testing required with sequence diagrams. There is no conversion required of existing projects. Undo ==== I'd like to continue this work but will come across difficulties with how to undo delete of a model element. I can't just store the delete model element as we'll get the familiar removed element exceptions from MDR. There are similar problems with undo of creating a model element. That would be to delete it and so how to redo? I'll get this as far as I can in all other areas. If anyone has any ideas then please start a sperate thread. Sequence Diagrams =============== The usability is still poor here and the existing code in need of major refactor. I think changes here will be piecemeal doing gradual improvements. Abandon zargo/uml Save Format ======================== I'm thinking of placing the PGML and TODO elements inside the XMI.extensions of the single XMI file. This is only at early investigation right now. This does not give us diagram interchange to other tools but is maybe a stepping stone in that direction. At least we are then using a standard extension mechanism. The benefits is in safety during zip save. At the moment ArgoUML can run out of memory when writing a zargo. The zip process itself is memory intensive. The user then loses their work. With a single xmi format we should save first as .xmi, then zip that single physical file, only deleting the .xmi if the zip fails. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
