When started, the new System Browser displays 6 major subviews and two toggle/filter panes; these are:
(the actual appearance of the Browser depends on the viewStyle setting; the picture above was taken with the "motif-style" in effect)
This default appearance is similar to the old browsers appearance; however, the popUpMenus as available in the various list views are duplicated in the browsers main menu panel.
By default, classes are grouped by their class category (as was the case with the old browser).
In this mode, all classes from all namespaces and all projects are shown together,
grouped only by their class category.
This aspect can be changed via the view-menu:
Viewmenu
You can change the grouping, by selecting one of the other items in the view-menu;
the most useful grouping is the Project view:
This enables you to organize your own projects into different packages.
For examples on typical uses of the browser, see the last section(s) of this document.
To switch, there are two toggle buttons named "class" and
"instance".
Selecting "instance" (which is the default) makes your changes
affect the class, and therefore affects the set of messages which are understood by instances;
selecting "class" lets you change the metaclass, and therefore affects the
set of messages which are understood by the class (typically instance creation and initialization messages).
If you are not too familiar with this concept, try the
Of course, this performs the same as evaluating "className
Double clicking on an unloaded (i.e. autoloaded) class, forces the class to be loaded into the system.
Double clicking on a subclass of TestCase will open the SUnit TestRunner on this testcase.
Double clicking on a method with a break- or trace-point will remove the break- or trace-point.
Double clicking on any other method will show all senders of that method.
"hierarchy"
function of the class-lists popupMenu - especially take a careful look at this
hierarchy when looking at the class protocol.
Double clicking on a class category
A double click on a class category will add a new buffer for browsing classes in that category.
Double clicking on a nameSpace
A double click on a nameSpace will add a new buffer for browsing classes in that nameSpace.
Initially, the namespace list is hidden - it can be made visible, by toggling the 'nameSpace' item in
the 'View' menu.
Double clicking on a project
A double click on a project will add a new buffer for browsing classes in that project.
Initially, the project list is hidden - it can be made visible, by toggling the 'project' item in
the 'View' menu.
Double clicking on a class
For your convenience, a double click on a class, which is
an application (i.e. subclass of ApplicationModel or a TopView application),
can be started (opened) by double clicking on the class.
(actually, any class which returns true from the #isVisualStartable query message
can be started this way)
open"
in a workspace.
Double clicking on a variable
Double clicking on a variable (in the variable-list) will show all methods which refer to that
variable (see also: variable search functions).
Double clicking on a method
For selectors, which are marked as windowSpec, menuSpec or imageSpec methods,
a corresponding editor application is opened on double-click.
That means, that a GUI-Painter is opened when you double-click a windowSpec method,
or an imageEditor is opened when you double-click an imageSpec method.
Doc $Revision: 1.9 $ $Date: 2001/09/10 20:02:24 $