I understand. I remember when I first saw that stuff!
Regards, Gary
----- Original Message -----
From: "Stéphane Ducasse" <[email protected]>
To: <[email protected]>
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"
<[email protected]>
To: <[email protected]>
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"
<[email protected]>
To: "pharo-project open-source Smalltalk"
<[email protected]>
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
