> Any reason a PackageInfo can't keep a list (set?) of the classes it contains?
> That would be more localised knowledge than having to make changes to
> systemorganization. It should speed up many of the includes* methods in
> PackageInfo.

I am currently working on a first-class Package that would replace PackageInfo.
A package is then defined by a name, a list of classes, and a list of methods.

It is available on SqueakMap, under the name MonticelloPackageBrowser.
I am continuing to work on the GUI part...

Alexandre

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.