Cross posting with the argoeclipse list as most answers are likely to come from there.
I do know that argoeclipse isn't necessarily a plugin for eclipse (although it can run as such). It does also run stand alone and I believe looks and acts just like standard ArgoUML when you do so. Regards Bob ---------- Forwarded message ---------- From: Mark Fortner <[email protected]> Date: 18 January 2011 17:56 Subject: Re: [argouml-dev] Module repository To: [email protected] I think there are a couple of points that Andreas is making: He doesn't use Eclipse, so if ArgoEclipse is merely a plugin for an IDE he doesn't use, then it will probably have limited use for him. The same could be said of most non-Eclipse users. Although I use Spring Tool Suite (a sort of kitchen-sink Eclipse distribution), I haven't quite figured out whether the extra overhead of adding yet another plugin to IDE is worth any performance degradation. There doesn't seem be a roadmap that indicates when (or if) ArgoEclipse will become the default distribution for ArgoUML. If this is going to happen this year, then Bob's statement about not "reinventing the wheel" probably holds. If it's going to be some indefinite time in the future, then it's probably worth looking at some short-term solution. Especially if there's a way of generating Eclipse update site XML from it. Under the rubric of "getting our ducks in order", it would also be useful if there was some discussion about the ArgoEclipse, in particular: Eclipse has a yearly release train, how will keeping up with that schedule effect the work that currently gets done? Will ArgoUML be distributed as a plugin, as a separate Eclipse distro, or both? How will the Eclipse RCP framework change ArgoUML's current module framework? Presumably, there would need to be some work either to bridge the two, or refactor all existing plugins to fit the Eclipse RCP API. What specific steps do plugin developers need to take in order to turn their existing plugins into Eclipse plugins? Are there any plans to document this in the wiki? Are there any plans to post a roadmap for some of the upcoming releases? This would help set some expectations, and keep everyone focused in the same general direction. Regardless of the approach we end up using to making modules "discoverable", the main thing we're all trying to achieve is improved ease of use and improved ease of development. Cheers, Mark ------------------------------------------------------ http://argoeclipse.tigris.org/ds/viewMessage.do?dsForumId=5521&dsMessageId=2698932 To unsubscribe from this discussion, e-mail: [[email protected]].
