That makes me shiver as well ;-) In Pharo 3 this luckily is not the case.I just have the philosophy to try and avoid putting things high in the hierarchy to make things high up as simple as possible (but not simpler ;-) ). This even considering class extensions.In this case, we can put the responsibility for some Roassal thingy in a Roassal builder so I would put that feature (and the added complexity) there.On Sep 29, 2014, at 10:23 AM, Tudor Girba <tudor@tudorgirba.com> wrote:What makes you shiver in this case?Object already defines its menu.Cheers,Doru_______________________________________________On Mon, Sep 29, 2014 at 1:41 PM, Johan Fabry <jfabry@dcc.uchile.cl> wrote:FWIW, I would prefer putting it in the builder. Putting things in Object always makes me shiver ...On Sep 29, 2014, at 1:50 AM, Tudor Girba <tudor@tudorgirba.com> wrote:_______________________________________________Hi,We need a simple way to add the Moose menu to any Roassal element or edge.We either- add RTInteractionBuilder>>menu: or,- add Object>>roassalMenuFor: aBuilderWhat do you think?
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--"Every thing has its own flow"
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev