[update 1.4] #14057
Locked
 
|
14057
----- - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor killing tha big monster - Part two. :) http://code.google.com/p/pharo/issues/detail?id=4513 Gary it would be good that you check because we have two ways to to a perform: accessor and setValueSelector while only one would be enough. Stef and Igor |
|
|
Some trickyness.
Use of a combined accessor vs. separate get/set selectors may cause some problems since less flexible. Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and UITheme helpers. Regards, Gary ----- Original Message ----- From: "Stéphane Ducasse" <[hidden email]> To: "pharo-project open-source Smalltalk" <[hidden email]> Sent: Friday, July 22, 2011 6:31 PM Subject: [Pharo-project] [update 1.4] #14057 14057 ----- - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor killing tha big monster - Part two. :) http://code.google.com/p/pharo/issues/detail?id=4513 Gary it would be good that you check because we have two ways to to a perform: accessor and setValueSelector while only one would be enough. Stef and Igor |
|
|
Did you check what we did?
Because it would give us some confidence :) Stef On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > Some trickyness. > > Use of a combined accessor vs. separate get/set selectors may cause some problems since less flexible. > Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and UITheme helpers. > > Regards, Gary > > ----- Original Message ----- From: "Stéphane Ducasse" <[hidden email]> > To: "pharo-project open-source Smalltalk" <[hidden email]> > Sent: Friday, July 22, 2011 6:31 PM > Subject: [Pharo-project] [update 1.4] #14057 > > > 14057 > ----- > > - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor killing tha big monster - Part two. :) > http://code.google.com/p/pharo/issues/detail?id=4513 > > Gary it would be good that you check because we have two ways to to a perform: accessor and setValueSelector while only one would be enough. > > Stef and Igor > |
|
|
I did check. Having a single accessor (with mutation) does not cover all the
cases. Some users require *no* getter, for instance, so would be erroneous to update in response to a change. Regards, Gary ----- Original Message ----- From: "Stéphane Ducasse" <[hidden email]> To: <[hidden email]> Sent: Monday, July 25, 2011 4:36 PM Subject: Re: [Pharo-project] [update 1.4] #14057 Did you check what we did? Because it would give us some confidence :) Stef On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > Some trickyness. > > Use of a combined accessor vs. separate get/set selectors may cause some > problems since less flexible. > Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and > UITheme helpers. > > Regards, Gary > > ----- Original Message ----- From: "Stéphane Ducasse" > <[hidden email]> > To: "pharo-project open-source Smalltalk" > <[hidden email]> > Sent: Friday, July 22, 2011 6:31 PM > Subject: [Pharo-project] [update 1.4] #14057 > > > 14057 > ----- > > - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor > killing tha big monster - Part two. :) > http://code.google.com/p/pharo/issues/detail?id=4513 > > Gary it would be good that you check because we have two ways to to a > perform: accessor and setValueSelector while only one would be enough. > > Stef and Igor > |
|
|
On Jul 25, 2011, at 6:08 PM, Gary Chambers wrote: > I did check. Having a single accessor (with mutation) does not cover all the cases. Some users require *no* getter, for instance, so would be erroneous to update in response to a change. Ok I finally got it :) we are open to change :) our goal was to clean the ugly "ok let us compile a method on the fly" Stef > > Regards, Gary > > ----- Original Message ----- From: "Stéphane Ducasse" <[hidden email]> > To: <[hidden email]> > Sent: Monday, July 25, 2011 4:36 PM > Subject: Re: [Pharo-project] [update 1.4] #14057 > > > Did you check what we did? > Because it would give us some confidence :) > > Stef > > On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > >> Some trickyness. >> >> Use of a combined accessor vs. separate get/set selectors may cause some problems since less flexible. >> Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and UITheme helpers. >> >> Regards, Gary >> >> ----- Original Message ----- From: "Stéphane Ducasse" <[hidden email]> >> To: "pharo-project open-source Smalltalk" <[hidden email]> >> Sent: Friday, July 22, 2011 6:31 PM >> Subject: [Pharo-project] [update 1.4] #14057 >> >> >> 14057 >> ----- >> >> - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor killing tha big monster - Part two. :) >> http://code.google.com/p/pharo/issues/detail?id=4513 >> >> Gary it would be good that you check because we have two ways to to a perform: accessor and setValueSelector while only one would be enough. >> >> Stef and Igor >> > > > |
|
|
In reply to this post by Gary Chambers-4
Are we talking about events/announcements? I ask because the Dolphin way of doing things like this is that #value: triggers events, #setValue: does not - more or less. It is a very nice system.
Caveat emptor: Dolphin also makes a lot of use of comparison policies (identity and equality being big players, of course). I have always suspected that these arose from a need to moderate/quench what might otherwise become a recursive meltdown of events in response to non-changes. Bill ________________________________________ From: [hidden email] [[hidden email]] On Behalf Of Gary Chambers [[hidden email]] Sent: Monday, July 25, 2011 12:08 PM To: [hidden email] Subject: Re: [Pharo-project] [update 1.4] #14057 I did check. Having a single accessor (with mutation) does not cover all the cases. Some users require *no* getter, for instance, so would be erroneous to update in response to a change. Regards, Gary ----- Original Message ----- From: "Stéphane Ducasse" <[hidden email]> To: <[hidden email]> Sent: Monday, July 25, 2011 4:36 PM Subject: Re: [Pharo-project] [update 1.4] #14057 Did you check what we did? Because it would give us some confidence :) Stef On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > Some trickyness. > > Use of a combined accessor vs. separate get/set selectors may cause some > problems since less flexible. > Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and > UITheme helpers. > > Regards, Gary > > ----- Original Message ----- From: "Stéphane Ducasse" > <[hidden email]> > To: "pharo-project open-source Smalltalk" > <[hidden email]> > Sent: Friday, July 22, 2011 6:31 PM > Subject: [Pharo-project] [update 1.4] #14057 > > > 14057 > ----- > > - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor > killing tha big monster - Part two. :) > http://code.google.com/p/pharo/issues/detail?id=4513 > > Gary it would be good that you check because we have two ways to to a > perform: accessor and setValueSelector while only one would be enough. > > Stef and Igor > |
|
|
We were talking about a kind of value holder which was played by MorphicModel and that was using a kind of accessor ( asymbol) and that gary extended.
And we are thinking that having a good one would be better to the accessor one. But we discovered that while cleaning slider. Stef On Jul 25, 2011, at 11:18 PM, Schwab,Wilhelm K wrote: > Are we talking about events/announcements? I ask because the Dolphin way of doing things like this is that #value: triggers events, #setValue: does not - more or less. It is a very nice system. > > Caveat emptor: Dolphin also makes a lot of use of comparison policies (identity and equality being big players, of course). I have always suspected that these arose from a need to moderate/quench what might otherwise become a recursive meltdown of events in response to non-changes. > > Bill > > > ________________________________________ > From: [hidden email] [[hidden email]] On Behalf Of Gary Chambers [[hidden email]] > Sent: Monday, July 25, 2011 12:08 PM > To: [hidden email] > Subject: Re: [Pharo-project] [update 1.4] #14057 > > I did check. Having a single accessor (with mutation) does not cover all the > cases. Some users require *no* getter, for instance, so would be erroneous > to update in response to a change. > > Regards, Gary > > ----- Original Message ----- > From: "Stéphane Ducasse" <[hidden email]> > To: <[hidden email]> > Sent: Monday, July 25, 2011 4:36 PM > Subject: Re: [Pharo-project] [update 1.4] #14057 > > > Did you check what we did? > Because it would give us some confidence :) > > Stef > > On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > >> Some trickyness. >> >> Use of a combined accessor vs. separate get/set selectors may cause some >> problems since less flexible. >> Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed and >> UITheme helpers. >> >> Regards, Gary >> >> ----- Original Message ----- From: "Stéphane Ducasse" >> <[hidden email]> >> To: "pharo-project open-source Smalltalk" >> <[hidden email]> >> Sent: Friday, July 22, 2011 6:31 PM >> Subject: [Pharo-project] [update 1.4] #14057 >> >> >> 14057 >> ----- >> >> - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor >> killing tha big monster - Part two. :) >> http://code.google.com/p/pharo/issues/detail?id=4513 >> >> Gary it would be good that you check because we have two ways to to a >> perform: accessor and setValueSelector while only one would be enough. >> >> Stef and Igor >> > > > > |
|
|
In reply to this post by Stéphane Ducasse
I understand. I remember when I first saw that stuff!
Regards, Gary ----- Original Message ----- From: "Stéphane Ducasse" <[hidden email]> To: <[hidden email]> Sent: Monday, July 25, 2011 8:17 PM Subject: Re: [Pharo-project] [update 1.4] #14057 On Jul 25, 2011, at 6:08 PM, Gary Chambers wrote: > I did check. Having a single accessor (with mutation) does not cover all > the cases. Some users require *no* getter, for instance, so would be > erroneous to update in response to a change. Ok I finally got it :) we are open to change :) our goal was to clean the ugly "ok let us compile a method on the fly" Stef > > Regards, Gary > > ----- Original Message ----- From: "Stéphane Ducasse" > <[hidden email]> > To: <[hidden email]> > Sent: Monday, July 25, 2011 4:36 PM > Subject: Re: [Pharo-project] [update 1.4] #14057 > > > Did you check what we did? > Because it would give us some confidence :) > > Stef > > On Jul 25, 2011, at 4:21 PM, Gary Chambers wrote: > >> Some trickyness. >> >> Use of a combined accessor vs. separate get/set selectors may cause some >> problems since less flexible. >> Users exist in Slider subclasses and DiffMorph. Plus the TEasilyThemed >> and UITheme helpers. >> >> Regards, Gary >> >> ----- Original Message ----- From: "Stéphane Ducasse" >> <[hidden email]> >> To: "pharo-project open-source Smalltalk" >> <[hidden email]> >> Sent: Friday, July 22, 2011 6:31 PM >> Subject: [Pharo-project] [update 1.4] #14057 >> >> >> 14057 >> ----- >> >> - Issue 4513: ScrollBar and MorphicModel needs cleaning. Stef and Igor >> killing tha big monster - Part two. :) >> http://code.google.com/p/pharo/issues/detail?id=4513 >> >> Gary it would be good that you check because we have two ways to to a >> perform: accessor and setValueSelector while only one would be enough. >> >> Stef and Igor >> > > > |
|
|
On Jul 26, 2011, at 10:18 AM, Gary Chambers wrote: > I understand. I remember when I first saw that stuff! lol :) this is a filter. People that faint should not continue coding in the UI ;) After all the *Plus and the rest we are making progress not as fast as I would like. Now I'm having as side project to clean the event loop with a nice double dispatch and really event and not buffer. Stef |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |