Hi,
Removing the typed groups would be a significant downgrade. The main power of Moose comes from the interplay between UI and queries.
The groups provide a simple mechanism for adding specific views. For example, System Complexity is a view that makes sense for a group of types and it’s defined in that class.
Also, the groups can also host queries. For example, from a group of types we can get commonExternalSuperclasses.
Cheers, Doru
On Jul 22, 2019, at 9:19 PM, Benoît Verhaeghe badetitou@gmail.com wrote:
Hi
I think the moose groups are used by the moose panel and the inspector to add some views on the inspect.
Benoît
Le lun. 22 juil. 2019 à 13:10, Cyril Ferlicot cyril.ferlicot@gmail.com a écrit : On Mon, Jul 22, 2019 at 11:49 AM Anne Etien anne.etien@univ-lille.fr wrote:
Hi,
We are currently cleaning the traits in FamixNG. Once again, the idea is to remove FamixCompatibility metamodel and to keep only FamixStEntities or FamixJavaEntities (and so on). Obviously, it has incidence on tests. Do you use FamixTypeGroup, FamixClassGroup… and more generally groups in Famix?
Hi,
Personally, I use sometimes MooseGroup but I never used all its subclasses.
Thank in advance for your answer.
Anne _______________________________________________ Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- Cyril Ferlicot https://ferlicot.fr _______________________________________________ Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev
-- feenk.com
"Be rather willing to give than demanding to get."