Hi all I've just had my first opportunity to download the argoeclipse project and see it in action. Well done Bogdan, great work.
Tom, looking back on this thread I understand more clearly now your issue with the persistence change. I'd like to somehow move forward to the xmi extension but support argoeclipse also. Is http://argouml.tigris.org/issues/show_bug.cgi?id=4431 acceptable? There are further issues with compatability of zargo projects with previous versions of ArgoUML which would also effect argoeclipse if its releases are out of step with ArgoUML. I need to rethink how the upgrade.xsl files and the persistence version work in ArgoUML, that will most likely give you a similar problem. Look out on the ArgoUML dev list and I'll raise it there. Bogdan said:
The ArgoEclipse project shouldn't be merged with ArgoUML. Take the example of Subclipse, Subclipse is not merged with SVN, they are distinct. ArgoUML, in my opinion, should do exactly the reverse, try to be a core project with just functionality, without GUI, it shouldn't rely upon Swing or SWT (as a plugin) or anything else, it should provide just the business logic for other GUI parts. This will allow the developers to focus on specifics
I think this makes sense although maybe the project can move more under the ArgoUML umbrella by becoming a subproject of ArgoUML. What Bogdan says is correct with regards to seperation of GUI and core ArgoUML. We have only been tiptoeing towards seperation of this and I hope the requirements of argoeclipse will speed this up. Whether the swing framework then becomes a seperate project is not so important to me so long as the build of core and swing gui is seperate with no cyclic dependancy. Bob. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
