January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Congrats

by Hilaire Fernandes

Waou! Go go Steph! Le 14/01/2011 17:17, Miguel CobÃ¡ a Ã©crit : > Congrats StÃ©ph, > > http://www.inria.fr/centre-de-recherche-inria/lille-nord-europe/actualites/… > > Cheers

Jan. 14, 2011

Re: [Pharo-project] [update 1.2] #12297

by Gary Chambers

Example: UITheme currentSettings windowColor: Color orange. World themeChanged. UITheme current class defaultSettings windowColor: Color lightBlue. World themeChanged. " no change" UITheme currentSettings windowColor: Color yellow. World themeChanged. UITheme current class beCurrent "uses default of light blue" Switching between themes uses the theme defaults rather than any modifications to the current theme. Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Friday, January 14, 2011 5:40 PM Subject: Re: [Pharo-project] [update 1.2] #12297 > Well, i imagine that different themes can have a different set of > editable settings available, > and from that perspective the ThemeSettings is limiting, since > it contains a list of 'standard' properties, no more no less. > > So, i proposing to rewrite all uses of: > > UITheme currentSettings foo > > with: > > UITheme current foo > > and let theme decide how to answer the requested value. > > For example, one could do: > > MyTheme>>fooColor > ^ Color red "non-editable, hardcoded value" > > while another one could decide to use color from settings: > > MyCoolTheme>>fooColor > ^ settings at: #fooColor default: Color red > > And also each theme could tell settings browser, which public > properties it having, > so, depending on currently installed theme, user could see and change > only those, which related to it. > > Then settings could be a simple dict, where keys is symbols and values > is property values. > and then, when you changing the current theme , it should simply do: > > newTheme settings: oldTheme settings > > so, nothing will be lost, even if new theme does not using some > properties, and when user will switching back to > old theme, it will continue using settings which already registered by/for > it. > > On 14 January 2011 18:05, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: >> Just FYI... >> On the class side of UITheme there is the defaultSettings... used when >> changing themes to initialise the new theme. >> Handy for having settings that survive theme changes. >> >> For those of you wanting to retain certain colour changes, this is the >> thing >> to edit. Should survive updates etc. >> >> Would be nice to have Settings support for both the current and defaults >> though ;-) >> >> Regards, Gary >> >> ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Friday, January 14, 2011 12:00 PM >> Subject: Re: [Pharo-project] [update 1.2] #12297 >> >> >>> On 14 January 2011 12:33, Douglas Brebner <squeaklists(a)fang.demon.co.uk> >>> wrote: >>>> >>>> On 13/01/2011 22:04, Tudor Girba wrote: >>>>> >>>>> That is a good point. I actually used the Sim Daltonism application >>>>> (for >>>>> Mac) to check the color blindness issues, but it looks like I >>>>> overlooked >>>>> Monochromacy (however, this is pretty rare). I will try to look into >>>>> that. >>>>> >>>>> Cheers, >>>>> Doru >>>> >>>> It's not just the colour blind that are affected (though they have it >>>> worst). Even people with perfect vision can find it difficult to >>>> distinguish >>>> adjacent areas of similar contrast. >>>> >>>> e.g. If you look at the save changes window that appears when quitting >>>> an >>>> image you'll notice the buttons almost disappear into the background. >>>> >>>> Still, it's good that someone is working on this :) >>>> >>> >>> yeah.. if you not cleaning your house, do not expect guests to come :) >>> >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Jan. 14, 2011

Re: [Pharo-project] [update 1.2] #12297

by Gary Chambers

Well, currentSettings is a delegation to the current theme settings... Is equivalent to UITheme current settings. Settings are abstracted out to declutter the theme. The point I was making is that there are settings on the current theme (volatile) and default settings per theme. I take your point, for ease of overriding, but the settings (as called) ware abstracted out since UITheme is already quite a large facade... I don't agree with settings being a dictionary, too many things are already inexplicit! Some kind of meta-description is appropriate though, for use in the Settings browser. Is that not the case already? Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Friday, January 14, 2011 5:40 PM Subject: Re: [Pharo-project] [update 1.2] #12297 > Well, i imagine that different themes can have a different set of > editable settings available, > and from that perspective the ThemeSettings is limiting, since > it contains a list of 'standard' properties, no more no less. > > So, i proposing to rewrite all uses of: > > UITheme currentSettings foo > > with: > > UITheme current foo > > and let theme decide how to answer the requested value. > > For example, one could do: > > MyTheme>>fooColor > ^ Color red "non-editable, hardcoded value" > > while another one could decide to use color from settings: > > MyCoolTheme>>fooColor > ^ settings at: #fooColor default: Color red > > And also each theme could tell settings browser, which public > properties it having, > so, depending on currently installed theme, user could see and change > only those, which related to it. > > Then settings could be a simple dict, where keys is symbols and values > is property values. > and then, when you changing the current theme , it should simply do: > > newTheme settings: oldTheme settings > > so, nothing will be lost, even if new theme does not using some > properties, and when user will switching back to > old theme, it will continue using settings which already registered by/for > it. > > On 14 January 2011 18:05, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: >> Just FYI... >> On the class side of UITheme there is the defaultSettings... used when >> changing themes to initialise the new theme. >> Handy for having settings that survive theme changes. >> >> For those of you wanting to retain certain colour changes, this is the >> thing >> to edit. Should survive updates etc. >> >> Would be nice to have Settings support for both the current and defaults >> though ;-) >> >> Regards, Gary >> >> ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Friday, January 14, 2011 12:00 PM >> Subject: Re: [Pharo-project] [update 1.2] #12297 >> >> >>> On 14 January 2011 12:33, Douglas Brebner <squeaklists(a)fang.demon.co.uk> >>> wrote: >>>> >>>> On 13/01/2011 22:04, Tudor Girba wrote: >>>>> >>>>> That is a good point. I actually used the Sim Daltonism application >>>>> (for >>>>> Mac) to check the color blindness issues, but it looks like I >>>>> overlooked >>>>> Monochromacy (however, this is pretty rare). I will try to look into >>>>> that. >>>>> >>>>> Cheers, >>>>> Doru >>>> >>>> It's not just the colour blind that are affected (though they have it >>>> worst). Even people with perfect vision can find it difficult to >>>> distinguish >>>> adjacent areas of similar contrast. >>>> >>>> e.g. If you look at the save changes window that appears when quitting >>>> an >>>> image you'll notice the buttons almost disappear into the background. >>>> >>>> Still, it's good that someone is working on this :) >>>> >>> >>> yeah.. if you not cleaning your house, do not expect guests to come :) >>> >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Jan. 14, 2011

Re: [Pharo-project] [update 1.2] #12297

by Igor Stasenko

Well, i imagine that different themes can have a different set of editable settings available, and from that perspective the ThemeSettings is limiting, since it contains a list of 'standard' properties, no more no less. So, i proposing to rewrite all uses of: UITheme currentSettings foo with: UITheme current foo and let theme decide how to answer the requested value. For example, one could do: MyTheme>>fooColor ^ Color red "non-editable, hardcoded value" while another one could decide to use color from settings: MyCoolTheme>>fooColor ^ settings at: #fooColor default: Color red And also each theme could tell settings browser, which public properties it having, so, depending on currently installed theme, user could see and change only those, which related to it. Then settings could be a simple dict, where keys is symbols and values is property values. and then, when you changing the current theme , it should simply do: newTheme settings: oldTheme settings so, nothing will be lost, even if new theme does not using some properties, and when user will switching back to old theme, it will continue using settings which already registered by/for it. On 14 January 2011 18:05, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: > Just FYI... > On the class side of UITheme there is the defaultSettings... used when > changing themes to initialise the new theme. > Handy for having settings that survive theme changes. > > For those of you wanting to retain certain colour changes, this is the thing > to edit. Should survive updates etc. > > Would be nice to have Settings support for both the current and defaults > though ;-) > > Regards, Gary > > ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Friday, January 14, 2011 12:00 PM > Subject: Re: [Pharo-project] [update 1.2] #12297 > > >> On 14 January 2011 12:33, Douglas Brebner <squeaklists(a)fang.demon.co.uk> >> wrote: >>> >>> On 13/01/2011 22:04, Tudor Girba wrote: >>>> >>>> That is a good point. I actually used the Sim Daltonism application (for >>>> Mac) to check the color blindness issues, but it looks like I overlooked >>>> Monochromacy (however, this is pretty rare). I will try to look into >>>> that. >>>> >>>> Cheers, >>>> Doru >>> >>> It's not just the colour blind that are affected (though they have it >>> worst). Even people with perfect vision can find it difficult to >>> distinguish >>> adjacent areas of similar contrast. >>> >>> e.g. If you look at the save changes window that appears when quitting an >>> image you'll notice the buttons almost disappear into the background. >>> >>> Still, it's good that someone is working on this :) >>> >> >> yeah.. if you not cleaning your house, do not expect guests to come :) >> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 14, 2011

[Pharo-project] Pharo issues on Google

by Gary Chambers

Is the Pharo issues google site not working? Regards, Gary

Jan. 14, 2011

Re: [Pharo-project] [update 1.2] #12297

by Gary Chambers

Just FYI... On the class side of UITheme there is the defaultSettings... used when changing themes to initialise the new theme. Handy for having settings that survive theme changes. For those of you wanting to retain certain colour changes, this is the thing to edit. Should survive updates etc. Would be nice to have Settings support for both the current and defaults though ;-) Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Friday, January 14, 2011 12:00 PM Subject: Re: [Pharo-project] [update 1.2] #12297 > On 14 January 2011 12:33, Douglas Brebner <squeaklists(a)fang.demon.co.uk> > wrote: >> On 13/01/2011 22:04, Tudor Girba wrote: >>> >>> That is a good point. I actually used the Sim Daltonism application (for >>> Mac) to check the color blindness issues, but it looks like I overlooked >>> Monochromacy (however, this is pretty rare). I will try to look into >>> that. >>> >>> Cheers, >>> Doru >> >> It's not just the colour blind that are affected (though they have it >> worst). Even people with perfect vision can find it difficult to >> distinguish >> adjacent areas of similar contrast. >> >> e.g. If you look at the save changes window that appears when quitting an >> image you'll notice the buttons almost disappear into the background. >> >> Still, it's good that someone is working on this :) >> > > yeah.. if you not cleaning your house, do not expect guests to come :) > >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

Jan. 14, 2011

[Pharo-project] Congrats

by Miguel CobÃ¡

Congrats StÃ©ph, http://www.inria.fr/centre-de-recherche-inria/lille-nord-europe/actualites/… Cheers -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Jan. 14, 2011

Re: [Pharo-project] Issue 3486 in pharo: PluggableTextMorph should be able to support text styling

by pharo＠googlecode.com

Updates: Status: Closed Comment #17 on issue 3486 by stephane...(a)gmail.com: PluggableTextMorph should be able to support text styling http://code.google.com/p/pharo/issues/detail?id=3486 in 12306

Jan. 14, 2011

Re: [Pharo-project] Issue 3417 in pharo: BehaviorTest>>#testAllLocalCallsOn fails

by pharo＠googlecode.com

Comment #4 on issue 3417 by stephane...(a)gmail.com: BehaviorTest>>#testAllLocalCallsOn fails http://code.google.com/p/pharo/issues/detail?id=3417 in 12305

Jan. 14, 2011

[Pharo-project] [update 1.2] #12305

by StÃ©phane Ducasse

12305 ----- - GLMOrangeUITheme beCurrent. - Issue 3417: BehaviorTest>>#testAllLocalCallsOn fails. Stef

Jan. 14, 2011