SystemNavigation and deprecated methods

Joshua 'Schwa' Gargus schwa at cc.gatech.edu
Tue Aug 12 14:56:19 UTC 2003


On Tue, Aug 12, 2003 at 02:29:11AM -0700, Colin Putney wrote:
> 
> On Tuesday, August 12, 2003, at 01:22 AM, Daniel Vainsencher wrote:
> 
> >On the new/default/global issue - at some point the KCP said that
> >making SysNavs behavior class side is bad. Now you're saying that
> >Globals are bad (or as Andreas notes, that non-class globals are bad).
> >Unless you want Squrak to lose its conciseness, something has to
> >give. And conciseness in programming languages is power.
> 
> Personally, I'd like to see something like 'self navigator' be the 
> default way of getting a SystemNavigator. Then there's lots of room for 
> overriding the default behaviour, in sort of the same way that classes 
> can specify which compiler class should be used to compile their 
> methods.

I have thought that SystemNavigator provides a good core for browsing
the capabilities of remote images.  'SystemNavigaton default' would
answer the SystemNavigaton for the current image, and 'SystemNavigaton
pid: processID' could return one on another Squeak instance.

I suppose this could be changed a bit to accomodate your vision.
'self navigator' could return the class-appropriate SystemNavigation
for the current image, and 'self navigatorForPID: processID' could
return one for another image.

Either of our approaches would be easy to move to should a need arise.
I think that sticking with 'SystemNavigation default' is the way to 
go for 3.6.

I confess that I can't think of a concrete use for your suggestion.
Care to broaden my horizons?

Thanks,
Joshua


> 
> Colin
> 



More information about the Squeak-dev mailing list