Agreed that is desirable. I was considering a "refresh" menu item but I like your idea better.
Also, what about the category list? Currently it is hand-crafted. It started out with only three
items: Pluggable, Morphic, and Morph. It grew to include anything that has four or more
children, but with Other Classes at the bottom. I've tried to reduce the Other Classes but it's
still 130+ in size for the base image.
The category list can be automatically generated from Smalltalk classNames by parsing for
all terms and acronyms. A name such as "RWBinaryOrTextStream" would generate five
categories: RW, Binary, Or, Text, and Stream. It seems that the up side would be elimination
of Other Classes since every class would be included in some category. Also, when
packages are loaded the list would be re-formed. The down side would be the list of
categories is longer and some categories would only have one to three children.
What do you think? Anyone have an opinion?
- Dan
On 21 Sep 2015 at 8:53, Ken.Dickey wrote:
> Dan,
>
> I would appreciate it if the Class Comment Browser would react to
> the same changed message that triggers the code browsers to update
> their state so that when new classes are loaded they show up in the
> browser.
>
> This saves me opening a new instance of the browser.
>
> Thanks a bunch for CCB!
> -KenD
_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org
Locked
