Monticello requires *PackageName for extensions to be included in the 
original package.


On 2023-01-01 16:20, Stephen Travis Pope wrote:
>
> Hello again,
>
> In reference to my previous query, when did it become fashionable to 
> have method category (protocol) names that signified the package?  How 
> does this help in navigating the system?
>
> It’s quite confusing when I go to a system class in the browser and 
> see a list of protocols like this,
>
> protocols.jpg
>
> Isn't there a field in the method header where we could store this, 
> and still use the simpler standard list of protocols to assist in 
> learning the system?  Remember, the first rule of reuse is, “if you 
> can’t find it, you can’t reuse it.”
>
> stp
>
> --------
>
> Stephen Travis Pope    Ojai,California, USA
> pastedGraphic.tiff
> http://HeavenEverywhere.com
> http://FASTLabInc.com
> https://vimeo.com/user19434036/videos
> http://heaveneverywhere.com/Reflections
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20230101/e4738920/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: protocols.jpg
Type: image/jpeg
Size: 122362 bytes
Desc: not available
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20230101/e4738920/attachment-0001.jpg>