Gary What I mean is that there are a lot of places where MenuMorph is hardcoded and the UIManager does not have a chance to take control. I imagine that this is for this reason that guillermo proposed this change.
Stef > Not sure what you mean but I'd expect high-level interactions to not ask for > a menuClass. > Still, in headless case, with this, it is possible to provide a suitable > replacement. > > Regards, Gary > > ----- Original Message ----- From: "Stéphane Ducasse" > <[email protected]> > To: "pharo Development" <[email protected]> > Sent: Friday, February 25, 2011 3:47 PM > Subject: [Pharo-project] About UIManager and UITheme for MenuMorph > > > Hi gary > > I was reading > http://code.google.com/p/pharo/issues/detail?id=3728 > which converts MenuMorph new -> UIManager default menuClass > > And I was wondering: > - UIManager regulate coarse grained interaction > > - UITheme takes into account settings > > Now UIManager does not provide handy MenuMorph creation method besides > choose.... and friends. > And now I'm looking at TEasilyThemed and it refers to MenuMorph so I'm > wondering if in headless > we could not still have popup menu raised. > > Stef >
