This is probably a stupid question, but it relates to something I have only
just noticed, having just tried to file in a package from SqueakMap. In the
Squeak system browser the classes are all grouped by categories, whereas in
Dolphin the equivalent classification is by packages. As far as I can see,
in Dolphin the class category can be defined and redefined, and it appears
as an infromation item in the browser title bar, but I cannot find any other
use for it. Am I missing something? (I have searched for references to
categories in the help files; the only mention of class categories seems to
be how to define them.)
> As far as I can see,
>in Dolphin the class category can be defined and redefined, and it appears
>as an infromation item in the browser title bar, but I cannot find any other
>use for it. Am I missing something?
Not really. As you say, they are mostly used for documentation
purposes, although they are occasionally used in other ways.
For example, the method
selects suitable TypeConverter classes using their ClassCategory.
The ImageStripper detects development classes by enumerating the
I would guess Class categories were implemented in Dolphin because
they are part of the original Smalltalk-80 (Red Book) UI, but to me
they still have a bit of a "solution looking for a problem" feel to
For Squeak, categories are like Packages in Dophin Smalltalk. It is
mandatory to choose a category for every class one make.
In Dolphin, it doesn't mean that much. It is just for organizing your
classes. I don't give categories for my classes for most of the cases.
Packaging is more important. I spend time for Packaging balancing,
prerequisits analysis, and spliting packages into VM independemt one
and VM dependent one.
Thanks Ian and Howard for your explanations; it's much clearer now. I raised
the issue because I found a fairly large Squeak 'package' with about 250
classes, which the author had organised into 6 categories. I had put all
these into one Dolphin package, and I just wondered whether it was worth
making them separate packages, and if so whether Dolphin provided any tools
to help in doing it. The answer to the second question is apparently 'no';
as to the first, dunno :-)
> I had put all
>these into one Dolphin package, and I just wondered whether it was worth
>making them separate packages, and if so whether Dolphin provided any tools
>to help in doing it. The answer to the second question is apparently 'no';
You don't really need a special tool for this, at least not unless you
want to get selective about what goes where.
Use the PackageManager to create the packages you want (XSamples and
XObjects in the example below).
Fix up the Category->Package mapping in the way you want ....