How to lockdown an image for release
Last updated at 9:24 am UTC on 31 October 2017
Question: How to lockdown the image for release
Answer: From: How to save a parts bin Sent: Sunday, December 14, 2003 12:15 PM
Use Ned Konz's Lockdown package.
This change set makes it easier to lock down an image for application delivery.
from your personalized World menu and saving the locked image under a new name, the following features are disabled:
- Meta and Debug menus
- Command keys in world
- Command-dot interrupts
- Debuggers (though notifiers will still come up)
- World menu (from mouse or key)
- Command keys other than editing & cursor in text
- Reading scripts/projects at startup.
The yellow-button menus in text panes will still come up. It is assumed that text panes in your app will have their own yellow-button menus.
Two existing preferences have been made available in the Preferences tool:
cmdKeysInText – enables the use of many cmd (or alt) keys in text editors
cmdGesturesEnabled – enables halos, debug menus, etc.
Another two new preferences have been added:
appendToErrorLog – appends to the error log rather than replacing it
noDebugButton – suppress the ability to open a debugger from a notifier
You can add this to your personalized World menu:
aMenu add: 'disable pgrmr' target: Preferences action:
Or you can add:
to your do... menu list.
Edgar J De Cleene suggested on the squeak-dev mailing list the following changes to the world menu:
TheWorldMenu - a simpler version
Also it makes sense to create a 'create release button' which does the necessary changes, destroys itself and saves the image.