I have to digest that because for now the infrastructure and relationship between UITheme UIManager UITheme builder is not clear to me. For example I do not understand why the builder is just a composableMorph and not a builder. especially since Pluggable and friend invoke theme anyway. At the end we should have something much clearer. For me the responsibilities are not clear. Stef On Jun 20, 2011, at 12:10 PM, Gary Chambers wrote:
Some theme methods require the context of creation (aThemedMorph as passed) for adapting to corner style, colours etc.
Perhaps, in TEasilyThemed, this context can be broken out into another method that MorphicUIManager could redefine as appropriate (guessing self world)...
Regards, Gary
----- Original Message ----- From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> To: <Pharo-project@lists.gforge.inria.fr> Sent: Monday, June 20, 2011 10:43 AM Subject: Re: [Pharo-project] why (UIManager defaultnewPluggableDialogWindow:'Pharo is cool') openInWorld
On Jun 20, 2011, at 11:11 AM, Gary Chambers wrote:
Because TEasilyThemed is designed to be applied to Morph subclasses... So when self (aMorphicUIManager) is passed to the theme it does not understand all Morph protocol.
Yes I saw but I still wonder why this is needed to "copy" all these protocols.
Regards, Gary
----- Original Message ----- From: "stephane ducasse" <stephane.ducasse@free.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <Pharo-project@lists.gforge.inria.fr> Sent: Saturday, June 18, 2011 6:58 PM Subject: [Pharo-project] why (UIManager default newPluggableDialogWindow:'Pharo is cool') openInWorld
why
(UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld
does not work? Apparently MorphicUIManager is missing something? Stef