Hello again!
This change could be added without breaking the current "Object
everywhere"-API. I agree with Tom that adding this is probably not something
we should undertake and I think this is because there is a lot of work
involved to create and maintain all the interfaces (and finding the right
path between UML1.4 and UML2.2).
/Linus
2009/5/29 Tom Morris <[email protected]>
> It's almost always easier to use an API to reference/read existing
> objects as compared to creating new objects, but which of the
> following is easier?
>
> ArgoNamedElement foo;
>
> 1. String name = Model.getFacade().getName(foo);
>
> 2. String name = foo.getName();
>
> particularly if you're using an IDE that lets you type "foo.get<meta
> key meaning show me all the options here>"?
>
> Now, this is *not* something that I'm proposing to change, but I've
> got an idea rattling around in the back of my head that style #2 could
> be implemented in a fashion similar to what MDR does by using the Java
> reflection API to inject Model API specific methods into MDR or eUML
> objects at run time.
>
> Tom
>
------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2356832
To unsubscribe from this discussion, e-mail:
[[email protected]].
To be allowed to post to the list contact the mailing list moderator, email:
[[email protected]]
