[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
On Jun 18, 2011, at 7:58 PM, stephane ducasse wrote:
why
(UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld
does not work? Apparently MorphicUIManager is missing something? Stef
(ExampleBuilderMorph new newPluggableDialogWindow: 'Pharo is cool') openInWorld is working because ExampleBuilderMorph inherits from Morph and not from Object (UITheme builder newPluggableDialogWindow: 'Pharo is cool'; minimumExtent: 200@300) openInWorld similarly. Now there is something that I do not understand. What is the use of the builder since I cannot pass it specific setting (UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new); beUnresizeable <<< does not work because the builder (a ComposableMorph does not pass such setting to the PluggableDialogWindow. ) openInWorld I would really like to have a nice kernel that support well such approach. In fact I imagine that we should not use UITheme builder that way. Stef
Hi Stef, I have no idea about the answers to your question. But looking into this is important. Cheers, Alexandre On 18 Jun 2011, at 15:02, Stéphane Ducasse wrote:
On Jun 18, 2011, at 7:58 PM, stephane ducasse wrote:
why
(UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld
does not work? Apparently MorphicUIManager is missing something? Stef
(ExampleBuilderMorph new newPluggableDialogWindow: 'Pharo is cool') openInWorld
is working because ExampleBuilderMorph inherits from Morph and not from Object
(UITheme builder newPluggableDialogWindow: 'Pharo is cool'; minimumExtent: 200@300) openInWorld
similarly.
Now there is something that I do not understand. What is the use of the builder since I cannot pass it specific setting
(UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new); beUnresizeable <<< does not work because the builder (a ComposableMorph does not pass such setting to the PluggableDialogWindow. ) openInWorld
I would really like to have a nice kernel that support well such approach. In fact I imagine that we should not use UITheme builder that way.
Stef
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I'm starting to write one chapter on basic widgets and I would like to understand and record it. And also modify the system to be consistent. Stef On Jun 18, 2011, at 9:56 PM, Alexandre Bergel wrote:
Hi Stef,
I have no idea about the answers to your question. But looking into this is important.
Cheers, Alexandre
On 18 Jun 2011, at 15:02, Stéphane Ducasse wrote:
On Jun 18, 2011, at 7:58 PM, stephane ducasse wrote:
why
(UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld
does not work? Apparently MorphicUIManager is missing something? Stef
(ExampleBuilderMorph new newPluggableDialogWindow: 'Pharo is cool') openInWorld
is working because ExampleBuilderMorph inherits from Morph and not from Object
(UITheme builder newPluggableDialogWindow: 'Pharo is cool'; minimumExtent: 200@300) openInWorld
similarly.
Now there is something that I do not understand. What is the use of the builder since I cannot pass it specific setting
(UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new); beUnresizeable <<< does not work because the builder (a ComposableMorph does not pass such setting to the PluggableDialogWindow. ) openInWorld
I would really like to have a nice kernel that support well such approach. In fact I imagine that we should not use UITheme builder that way.
Stef
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Can I participate ? Ben On Jun 19, 2011, at 8:53 AM, Stéphane Ducasse wrote:
I'm starting to write one chapter on basic widgets and I would like to understand and record it. And also modify the system to be consistent.
Stef
On Jun 18, 2011, at 9:56 PM, Alexandre Bergel wrote:
Hi Stef,
I have no idea about the answers to your question. But looking into this is important.
Cheers, Alexandre
On 18 Jun 2011, at 15:02, Stéphane Ducasse wrote:
On Jun 18, 2011, at 7:58 PM, stephane ducasse wrote:
why
(UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld
does not work? Apparently MorphicUIManager is missing something? Stef
(ExampleBuilderMorph new newPluggableDialogWindow: 'Pharo is cool') openInWorld
is working because ExampleBuilderMorph inherits from Morph and not from Object
(UITheme builder newPluggableDialogWindow: 'Pharo is cool'; minimumExtent: 200@300) openInWorld
similarly.
Now there is something that I do not understand. What is the use of the builder since I cannot pass it specific setting
(UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new); beUnresizeable <<< does not work because the builder (a ComposableMorph does not pass such setting to the PluggableDialogWindow. ) openInWorld
I would really like to have a nice kernel that support well such approach. In fact I imagine that we should not use UITheme builder that way.
Stef
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
you are welcome :) I think that I will log all the things I learn slowly and we will try to fix the inconsistency. My first notes are in the basicWidgets chapter on pbe On Jun 19, 2011, at 12:36 PM, Benjamin wrote:
Can I participate ?
Ben
On Jun 19, 2011, at 8:53 AM, Stéphane Ducasse wrote:
I'm starting to write one chapter on basic widgets and I would like to understand and record it. And also modify the system to be consistent.
Stef
On Jun 18, 2011, at 9:56 PM, Alexandre Bergel wrote:
Hi Stef,
I have no idea about the answers to your question. But looking into this is important.
Cheers, Alexandre
On 18 Jun 2011, at 15:02, Stéphane Ducasse wrote:
On Jun 18, 2011, at 7:58 PM, stephane ducasse wrote:
why
(UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld
does not work? Apparently MorphicUIManager is missing something? Stef
(ExampleBuilderMorph new newPluggableDialogWindow: 'Pharo is cool') openInWorld
is working because ExampleBuilderMorph inherits from Morph and not from Object
(UITheme builder newPluggableDialogWindow: 'Pharo is cool'; minimumExtent: 200@300) openInWorld
similarly.
Now there is something that I do not understand. What is the use of the builder since I cannot pass it specific setting
(UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new); beUnresizeable <<< does not work because the builder (a ComposableMorph does not pass such setting to the PluggableDialogWindow. ) openInWorld
I would really like to have a nice kernel that support well such approach. In fact I imagine that we should not use UITheme builder that way.
Stef
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Just the parenthesis placement... (UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new)) beUnresizeable; openInWorld Regards, Gary ----- Original Message ----- From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> To: <Pharo-project@lists.gforge.inria.fr> Sent: Saturday, June 18, 2011 8:02 PM Subject: Re: [Pharo-project] why (UIManager defaultnewPluggableDialogWindow: 'Pharo is cool') openInWorld On Jun 18, 2011, at 7:58 PM, stephane ducasse wrote:
why
(UIManager default newPluggableDialogWindow: 'Pharo is cool') openInWorld
does not work? Apparently MorphicUIManager is missing something? Stef
(ExampleBuilderMorph new newPluggableDialogWindow: 'Pharo is cool') openInWorld is working because ExampleBuilderMorph inherits from Morph and not from Object (UITheme builder newPluggableDialogWindow: 'Pharo is cool'; minimumExtent: 200@300) openInWorld similarly. Now there is something that I do not understand. What is the use of the builder since I cannot pass it specific setting (UITheme builder newPluggableDialogWindow: 'Pharo is cool' for: (RectangleMorph new); beUnresizeable <<< does not work because the builder (a ComposableMorph does not pass such setting to the PluggableDialogWindow. ) openInWorld I would really like to have a nice kernel that support well such approach. In fact I imagine that we should not use UITheme builder that way. Stef
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. 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
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
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
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
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 component creation. 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... Regards, Gary ----- Original Message ----- From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> To: <Pharo-project@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 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
participants (5)
-
Alexandre Bergel -
Benjamin -
Gary Chambers -
stephane ducasse -
Stéphane Ducasse