Although I've been involved with the development of ArgoUML, currently there is another UML editing open source tool which is getting enough track to gain my attention. This is Papyrus. It is RCP and EMF based from its conception, i think.
So, it should be less complex to proceed from it than to proceed from ArgoUML, which must progress in the painful way from an architecture oriented towards Java Swing and NetBeans MDR (the project was abandoned by NetBeans). As a user of ArgoUML, which would be the most interesting features to bring from ArgoUML into Papyrus?...
- critics
- varied module ecosystem;
- plenty of programming languages supported?
- some concrete specific features that users can't live without;
- some well supported translations;
- (meta '("missed something?"))
So, my basic idea is to try to introduce into Papyrus some of the features that ArgoUML has which could add value to Papyrus as a UML editing and visualization tool. At least i could start from there. This blog would continue to be called Argonaut's life, obviously :-)
But you must always start by using the tool and fix a simple bug before delving into some process like this. Guess what - i never used it!?!