Is there a mechanism for this? Say I want to add some actions to
SequenceableCollection's Items presentation without overriding the existing
method...
Also, is there a canonical documentation for GT? I found the blog posts, and
the presentation documentation in the Moose book, but nothing about GT's
hooks (e.g. my question above).
Thanks!
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Extending-an-Existing-GT-Presentation-tp4913845.html
Sent from the Moose mailing list archive at Nabble.com.
Hi,
I think that the #atScope: changed in Moose 6 but it seems that
MooseOutgoingCompositeQueryResult still uses the old #atScope.
To see the problem you can just copy this test in MooseQueryTest:
testProblemAtScope
self shouldnt: [ class2 querySureOutgoingAssociations atTypeScope ]
raise: MessageNotUnderstood
--
Cyril Ferlicot
http://www.synectique.eu
165 Avenue Bretagne
Lille 59000 France
Hi,
We have an engineer position at Lille (France) in the RMOD team to modernize FAME, FAMIX and software analysis tools.
The position is for two years starting in November or December. Conditions to apply are to have a master with 2 to 10 years of experience.
Industrial applications of Moose have shown some limits: (1) problem to scale, (2) modularity and extensibility and (3) user syntax. To overtake these limits, it becomes essential to modernize Moose heart. This project has three major objectives: (i) reduce the memory print to enable a better scaling, (ii) modernize Moose heart to introduce more modularity and extensibility and (iii) simplify the use and extension of Moose.
This project aims to develop a new version of Moose (Moose 2.0) more modular, less memory consumer and easier to use. Advantages of Platypus (PL)(http://dossen.univ-brest.fr/apl/index.php/Platypus <http://dossen.univ-brest.fr/apl/index.php/Platypus>) a research prototype developed in Pharo to analyse software systems as models will be combined to those of the current Moose (M) version and the new features of Pharo (P).
Moose 2.0 = flexible metamodel (M) supporting multiple inheritance and union of types (PL) + user syntaxto simplify model specifications (PL)
+ lot of analysis and visualization tools (M)
+ tool infrastructure (M)
+ model generator (PL)
+ compatibility with industrial and academic standard (PL) + low memory print (P)
+ access to method details (M) on demand (P)
Mission description (in French) and application form are available here (https://www.inria.fr/institut/recrutement-metiers/offres/ingenieurs-r-d-con… <https://www.inria.fr/institut/recrutement-metiers/offres/ingenieurs-r-d-con…>).
French is not mandatory whereas English is ;o)
If you have questions, don’t hesitate to ask.
Sincerely,
Anne Etien
