It's just how Monticello works out which methods go in which packages. I agree it can result in some clumsiness but it is very simple to implement and perhaps more importantly, to explain to users.

> On 2023-01-01, at 1:20 PM, Stephen Travis Pope <stephen at heaveneverywhere.com> 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
> 
> 
> 
> 


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Oxymorons: Soft rock