Re: [Pharo-users] Inspecting calculated attributes

2017-02-15 Thread Alistair Grant
On 15 February 2017 at 18:45, Sven Van Caekenberghe wrote: > > A custom extension is soo easy to do and will probably fit your expectations > better. It would not be much more work than listing/indicating which > attributes > you want to display. My original thought was to use method pragmas to

Re: [Pharo-users] Inspecting calculated attributes

2017-02-15 Thread denker
> > I added this as an example to the Slot package: > > https://pharo.fogbugz.com/f/cases/19709/add-example-ComputedSlot > > > This will be in the next update. > > Very cool !! > A good example would be calculation ba

Re: [Pharo-users] Inspecting calculated attributes

2017-02-15 Thread Ben Coman
On Wed, Feb 15, 2017 at 6:43 PM, denker wrote: > > On 15 Feb 2017, at 11:24, denker wrote: > > > On 15 Feb 2017, at 10:56, Ben Coman wrote: > > > > On Wed, Feb 15, 2017 at 3:38 PM, Alistair Grant > wrote: > I'm developing a number of classes where it would be convenient to be > able to inspect

Re: [Pharo-users] Inspecting calculated attributes

2017-02-15 Thread denker
> On 15 Feb 2017, at 11:24, denker wrote: > > >> On 15 Feb 2017, at 10:56, Ben Coman wrote: >> >> >> >> On Wed, Feb 15, 2017 at 3:38 PM, Alistair Grant >> wrote: >> I'm developing a number of classes where it would be convenient to be >> able to inspect what might be described as calculat

Re: [Pharo-users] Inspecting calculated attributes

2017-02-15 Thread denker
> On 15 Feb 2017, at 10:56, Ben Coman wrote: > > > > On Wed, Feb 15, 2017 at 3:38 PM, Alistair Grant wrote: > I'm developing a number of classes where it would be convenient to be > able to inspect what might be described as calculated attributes, i.e. > the result of a unary message send. T

Re: [Pharo-users] Inspecting calculated attributes

2017-02-15 Thread Ben Coman
On Wed, Feb 15, 2017 at 3:38 PM, Alistair Grant wrote: > I'm developing a number of classes where it would be convenient to be > able to inspect what might be described as calculated attributes, i.e. > the result of a unary message send. The result isn't stored in an > instance variable, but is

Re: [Pharo-users] Inspecting calculated attributes

2017-02-14 Thread Sven Van Caekenberghe
> On 15 Feb 2017, at 08:38, Alistair Grant wrote: > > I'm developing a number of classes where it would be convenient to be > able to inspect what might be described as calculated attributes, i.e. > the result of a unary message send. The result isn't stored in an > instance variable, but is st

[Pharo-users] Inspecting calculated attributes

2017-02-14 Thread Alistair Grant
I'm developing a number of classes where it would be convenient to be able to inspect what might be described as calculated attributes, i.e. the result of a unary message send. The result isn't stored in an instance variable, but is still useful when inspecting. I can obviously develop an inspect