[Pharo-project] why (UIManagerdefaultnewPluggableDialogWindow:'Pharo is cool') openInWorld
gazzaguru2 at btinternet.com
Tue Jun 21 04:49:15 EDT 2011
UITheme - Theme specific look/feel and main "services" (dialogs for choosing
fonts, colours etc.)
TEasilyThemed - Trait facade with lighter-weight helpers for services and UI
UIManager - Was, in Squeak, a facade for basic services (request text etc.).
Now incorporates TEasilyThemed
UITheme builder - an entry point for using TEasilyThemed if not
desired/appropriate to incorporate the trait into the sender
Since UIManager now incorporates TEasilyThemed, UITheme builder might as
well reference UIManager default...
----- Original Message -----
From: "Stéphane Ducasse" <stephane.ducasse at inria.fr>
To: <Pharo-project at lists.gforge.inria.fr>
Sent: Monday, June 20, 2011 7:41 PM
Subject: Re: [Pharo-project] why
(UIManagerdefaultnewPluggableDialogWindow:'Pharo is cool') openInWorld
I have to digest that because for now the infrastructure and relationship
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.
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 at inria.fr>
> To: <Pharo-project at 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
>> Regards, Gary
>> ----- Original Message ----- From: "stephane ducasse"
>> <stephane.ducasse at free.fr>
>> To: "An open mailing list to discuss any topics related to an
>> open-sourceSmalltalk" <Pharo-project at lists.gforge.inria.fr>
>> Sent: Saturday, June 18, 2011 6:58 PM
>> Subject: [Pharo-project] why (UIManager default
>> newPluggableDialogWindow:'Pharo is cool') openInWorld
>>> (UIManager default
>>> newPluggableDialogWindow: 'Pharo is cool') openInWorld
>>> does not work?
>>> Apparently MorphicUIManager is missing something?
More information about the Pharo-dev