10 Jun
2011
10 Jun
'11
3:06 p.m.
Hi Nicolas,
On 10 Jun 2011, at 14:06, Nicolas Anquetil wrote:
When working on eclipse, I discovered the necessity to represents things like plugins or
components which are not directly handled in Famix.
It is important if we want to be able to deal with real world cases.
I am not sure I understand. Could you be more specific?
May be we should consider introducing them as Moose
Entities?
FAMIX is meant to be extended. For example, to model JEE systems, we added entities like
EntityBean or SessionBeans.
Or may be not: I used Moose-Groups (of class because
one package can be spread over different plugins) and it is not that bad.
the main issue, in my case, was that classes don't know to what group they have been
assigned...
Groups are not meant to work bidirectionally. But, perhaps it would be an interesting
addition to try to add this information.
So computing dependencies could be very lengthy.
I solved that by creating a dictionary on the side, but maybe we should think on a better
solution.
And then of course integrate this with all the tools...
Interesting. I would be interested in hearing the actual cases.
Cheers,
Doru
nicolas
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"It's not how it is, it is how we see it."