> I hope I haven't violated the spirit of community voting. If > I have, I apologize for that.
I don't see a problem with doing what it takes to get a feature that you are interested in implemented. Having said that, I think you may be overestimating the usefulness of voting in achieving implementation. What's really needed is more developer resources. My personal Argo to-do list never gets short enough that I'm scouring the issue database for more work to do. The particular issue that you're talking about is one that I've never voted for, but have done work on. > About a month ago, I initiated email discussions with some of > the developers of AndroMDA http://www.andromda.org/ , > regarding what they needed to switch from Magic Draw to ArgoUML. I think making it *possible* for the AndroMDA developers to use ArgoUML for their work is a good goal, but I wouldn't hold my breath waiting for them to switch once it is possible. There very well may be non-technical factors (political, financial, familiarity, etc) at play. If they were to switch, it would provide them with no real benefit and it would require them redo all their diagrams for their profiles and sample projects. The fact that the tool that the AndroMDA developers use makes such a big difference really highlights the complete failure of the OMG to do its job properly. It's only in the past few months with the arrival of UML 2.1 that it's become possible for modeling tools to actually achieve useful interchange. It'll take some time for this availability to ripple down through the food chain. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
