2010/3/3 Stéphane Ducasse <[email protected]>:
>> 1) Rename Browser -> SystemBrowser
>> 2) Rename SystemNavigation -> Browser
>> 3) move SystemNavigation methods -> class side
>
> Why not
>        Navigator
>        Finder and we do not change all the existing books that always called 
> Browser the tool
>
>        Finder allCallOn: #new
> Stef

Yes, that works too.

I don't fear the confusion of Browser the finder and SystemBrowser the tool :
- because with all browse messages implemented in the finder, it can
be viewed as the mean to access the tool
- because advanced users wishing to program will just discover the
subtle implementation difference by browsing

But then, I don't care that much

Nicolas

>>
>> Rationale:
>> 1) that's what is written in window title, isn't it ?
>> 2) Browser allCallsOn: and Browser browseAllCallsOn: are so neat !
>> 3) Is there any value in instance side, or is SystemNavigation just a 
>> factory ?
>>
>> Browser would not designate the tool, but the friendly compagnon used
>> to browse and query.
>> You can easily create a few compatibility hooks to SystemBrowser if required.
>>
>> Nicolas
>>
>>>> The important thing if this becomes the solution, is deciding what goes
>>>> where, (in a consistent fashion across forks),
>>>
>>> I'm sure that we will be able to have something that is cross fork. I do 
>>> not have the energy
>>> to argue.
>>>
>>>> as well as the level of
>>>> backwards-compatibility packages should be offered/deprecation methods
>>>> kept in the image.
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to