Clotilde Toullec
Clotilde Toullec
Tests meant to show expected behavior when removing all traits from a class. Failing for now. Related to #8549
#mooseInterestingEntity converts collections to MooseGroups but I fear this is not optimized and iterates over it. Check if this can be optimized.
Comment this in baseline
There is almost no organization in this package, no common prefix, some unused classes. To be short, there is cleaning to do.
When graph algorithms are fixed/improved and migrated to pharo-ai, we should remove them from Moose and use [pharo-ai](https://github.com/pharo-ai) directly
- Some groups are specialized (All classes is a FamixClassGroup) and some are not (All packages is a MooseGroup). - There are some repetitions (All classes and All FamixStClasses, that...
Lint Rules in: - Moose-Core: - ```FAMIXMetaModelClassesNotDeclaredInFameRule``` - ```FAMIXMetaModelClassesShouldNotOverrideRule``` - Fame-Rules: - ```FameNameConventionBetweenFM3AndSmalltalkRule``` - ```FameSuperclassMetaDescribedExistRule``` - ```FameOppositeAttributeShouldPointBackRule``` - ```FameOppositeClassNotExistRule``` do not respond to P9 rules API (```#enabledSettingID```). Should we keep...
After a small change in the code, the proposed commit is the deletion of the whole package. This appeared in a Moose 8 image (Pharo 8), after loading [Midas](https://github.com/moosetechnology/Midas) (including...
Try to use the organization variable PHARO_VERSIONS
This example shows a very nice toolbar, blending in the theme, no color whatsoever. ```Smalltalk toolbar := SpToolbarPresenter new. toolbar addItem: (SpToolbarButtonPresenter new label: 'Button' ; color: Color blue; borderColor:...