Hi Marcos,
About your feature suggestions, what do you mean by:
"Make the profiles exportable, once loaded in a project.
I.e. export profile as XMI.
This will allow extending e.g. the Java profile."
Well, the user will only see the presence of the Java profile in the new
dialog you built. For him, there is no way to see the contents of the XMI
file that describes this profile.
Developers can of course obtain org.argouml.default-java.xmi directly, but
for the common user, it would be practical to export this file, i.e. create
it from within ArgoUML. Then he can e.g. add some more Java classes, and
reload it in his ArgoUML project.
All this is about the way the common ArgoUML user will deal wth profiles. He
needs to be able to easily do small adaptations to the default profiles.
This is very similar to adapting the normal.dot for MSWord.
One more point:
Suppose I create a profile, and use it on a project. Then I want my
colleague to work on the project, so I send him the zargo file.
This scenario shows, that it would be best, if the loaded profiles are
stored in the zargo file.
Regards,
Michiel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
