Hi Darius,

Thanks for the pointers. I remembered that that Wiki page about locking
things down existed but I went looking for it a while back and couldn't
seem to find it. I need to work on my googling skills a bit I guess.

James does indeed make some good points in the blog entry you mention.
>From my experience I certainly agree that is it highly advantageous and
convenient to have development and debugging tools available in version
for software that is deployed to users "in the wild", but I have also
found that it is often best to hide those sorts of things from the
causal user. Their presence often distracts people from focusing on the
job at hand. But if the availability of debug and development tools can
be "switched on", say via command line arguments or a (not commonly
used) key stroke combination when required by power users and/or
technical support people and/or developers then that is often a good way
to go.

Ron
----------=-=-=-=-=-=-=-=-========oOo========-=-=-=-=-=-=-=-=----------
mailto:Ronald.P.Welch at BAESYSTEMS.com                Phone:(607)770-3701
BAE SYSTEMS                     600 Main St Johnson City, NY 13790-1888
----------=-=-=-=-=-=-=-=-===================-=-=-=-=-=-=-=-=---------- 
-----Original Message-----
From: Darius Clarke [mailto:socinian at gmail.com] 
Sent: Friday, December 09, 2005 1:15 PM
To: The general-purpose Squeak developers list
Subject: Re: What does Squeak application development look like?

For lockdown see:

"How to lockdown an image for release"
http://minnow.cc.gatech.edu/squeak/518
By executing:
	Preferences disableProgrammerFacilities
from your personalized World menu and saving the locked image under a
new name, the following features are disabled:
          o Halos
          o Meta and Debug menus
          o Command keys in world
          o Command-dot interrupts
          o Debuggers (though notifiers will still come up)
          o World menu (from mouse or key)
          o Command keys other than editing & cursor in text
          o Reading scripts/projects at startup.
___

James Robertson makes a good case for keeping most of the develoment
environment in the customer release image (rapid bug fixes, very
accurate diagnosis, etc.).
You can search his blog:
http://www.cincomsmalltalk.com/blog