It does NOT make sense, to turn this off.
It does not make sense, to turn this on, since the change file will probably grow to a huge size over time.
If multiple users are working in the same directory, it is recommended, to use separate changeFiles (updates are not automatically synchronized).
Changing the name temporarily may also be useful to separate changes done in different projects.
If enabled, sourceCode
will be aquired from a sourceCodeManager.
A classes sourceCode is accessed by its revision number, its module and
directory. If configured correctly, no local sourcefiles need to be present.
Using the sourceCodeManager requires that a proper source repository has been setup, the CVS sourcecode management system has been installed and the files are accessable either directly or via a TCP/IP link.
If your CVS repository is accessable in your fileSystem (i.e.
the repository is either on a local drive or NFS-mounted),
enter the CVS root directory into the 'repository' field.
Otherwise, if the repository is to be accessed via a TCP
link in server mode, prefix the root directory by the
hostname of your repository server.
We recommend setting the shell environment variable
"CVSROOT" to the root directory or server path,
before starting Smalltalk/X. This can be done in your
"autoexec.bat" (win32) or .profile
(unix) or ".login" script.
When sources are accessed via the source code management, this may take some
time (the source has to be extracted via RCS and also, the access may
be to a remote machine).
Therefore, extracted source files are cached in a local directory.
By default, this directory is "/tmp/stx_sourceCache.
This field allows you to change that directory
(required on many sunos
installations, where the default "tmp" partition is too small).
Notice, that if a common sourceCache directory is used, it should be read/write/executable for all users.
Also notice, that you may clean this directory at any time - there is no danger involved, except for a (possibly slow) repository-refetch when a source file is requested the next time.
Using local source access is recommended if classes have been compiled from
modified local files, and the classes revision number does not reflect the
actual revision.
(i.e. if source files have been modified & compiled,
but not yet checked back into the repository).
The formatter may be configured to either generate lisp-style or c-style block format.
Warning: the formatter is based on the BRFormatter code ported from the RefactoryBrowser package. Porting is still underway and there may be bugs especially with ST/X extended syntax. Use at your own risk.
Developers might prefer the default, which is to go into the debugger immediately (saves another confirmation-click).
"Block>>value" and some other less
interesting stuff) are hidden, or in verbose mode, where all contexts
are shown.
This toggle controls the default, to be used by a debugView initially.
(Notice, that the debugViews popUpMenu always allows the mode of to be
changed later.)
Most people prefer the dense mode, which shows a less confusing, compact backtrace.
Copyright © Claus Gittinger Development & Consulting, all rights reserved