********************************** Triton Preferences Editor Release 1.1 (c) 1993-1994 Stefan Zeiger ********************************** Contents ======== 1. Introduction 2. Installation 3. Using the editor 4. Program history 1. Introduction =============== The Triton Preferences Editor allows you to customize the look and feel of applications which are using the Triton GUI creation system. The Preferences Editor is shareware. In unregistered versions only the system options are saved. Registered Triton users/developers will get a keyfile which unlocks the editor. See the file 'Distribution' in the main directory of this Triton distribution for more information about registering. 2. Installation =============== First of all, Triton requires at least OS2.04. If you're still running 1.2 or 1.3, you have to upgrade to OS2.04 or better. If you're running OS2.04 or 2.05 (v37), you have to install reqtools.library (© Nico François) in order to use the screenmode selection in the public screen manager. Beginning with OS2.1 (v38) the ASL screenmode requester will be used if ReqTools is not available. The Triton Preferences Editor can be installed by hand by simply dragging it into the 'Prefs' drawer of your boot partition ('sys:Prefs'). Then start the editor and confirm that you want to install the Preferences System. It may be removed again later by selecting 'Project/Remove' in the editor's main window's menu. The preferred method of installing the editor is using the Triton installation script which also installs triton.library. 3. Using the editor =================== The Triton Preferences Editor allows you to change basically two kinds of settings: 1. Global settings for all Triton applications (e.g. public screens). 2. Private application settings. Note that the listed global application '««Global»»' belongs to the second type, too. If an application is created, it will inherit the global application's settings. Thus all applications without own settings will use the global settings. As soon as you change any setting of an application, it will become independant and will not inherit future changes of the global application. If you want to delete an application's private settings and make it use the global settings again (including inheriting future changes to them), select the menu item 'Edit/Reset To Global'. This system may sound a bit complicated to you, but it is quite easy to handle. Main window menu 'Edit': ~~~~~~~~~~~~~~~~~~~~~~~~ This menu contains all standard items plus 'Reset to Global' (see above). All changes made from within this menu do only apply to the currently selected application. Main window gadgets: ~~~~~~~~~~~~~~~~~~~~ 'Save', 'Use' and 'Cancel' should be self-explaning. They apply to all modified settings of all applications. 'Test' will restart the Preferences editor using the current settings without saving anything. 'Info' will give you all information available about the selected application. This includes name, version, compilation date and so on. 'Delete' will delete an application, i.e. its settings and information files. You have to restart the application to make it appear in the Triton Preferences Editor again. If you just want to delete an application's private settings, use 'Edit/Reset to Global' The gadget 'System' opens the system window which contains all global settings. All other gadgets open windows for private application settings. 'Frames' window: ~~~~~~~~~~~~~~~~ The frames window allows you to configure the look of frames and groups. This should be mostly self-explaining. 'Pens' window: ~~~~~~~~~~~~~~ You can change window backgrounds in this window. For each background you may select a pattern or alternatively a pen. 'Windows' window: ~~~~~~~~~~~~~~~~~ This window contains the Triton window manager. The list shows all windows of the selected application which have been opened since the last reboot or are saved permanently to 'envarc:Triton'. The windows are displayed by their titles (if available; otherwise the ID number in square brackets). If you close a Triton window, Triton will remember its last dimensions in a file in 'env:Triton', so that it will have the same dimensions when you reopen it. If you want to keep the window dimensions permanently, so that they are always available (unless you change them later on), select the appropriate window and click on 'Snapshot'. This system works just like the window snapshotting of the Amiga Workbench. If you want Triton to 'forget' a custom window position and reposition the window according to the original positioning information (e.g. centering the window on the screen after chosing a new screen resolution), you can 'UnSnapshot' the window. The gadgets 'Snapshot all' and 'UnSnapshot all' will (un)snapshot all windows of the currently selected application. The gadget 'Info' will bring up a requester containing some information about the currently selected window. 'System' window: ~~~~~~~~~~~~~~~~ The system window contains all global settings. Currently only the public screen manager is included here. You can add, delete and edit public screens. Double click on a screen or select 'Use' and the name of the screen will be copied into the above string gadget. This is the screen for the currently selected application. You may also type in any other screen name. When Triton opens a window, it will first look if the specified screen exists and utilize it in this case. Otherwise it will try to create it if an entry for this screen can be found in the screen manager. If this doesn't work either, Triton will fall back onto the default public screen. You can test how a screen will look by selecting 'Test'. The screen will be opened and can be closed again by closing the information window which is displayed in it. The screen will not be made public when testing. Note that the screen manager settings override any specifications made by the programmer. Setting an application's screen to '«Program default»' will make it use the screen specified by the programmer. Anyhow only public and workbench screen windows can be promoted using the screen manager. Custom screen windows will always open on the custom screen specified in the program. 4. Program History ================== ***************************************************************************** RELEASE 1.1 (Version 2.74) First release. ***************************************************************************** __ __/// \\\/...if(2B|!2B) user->prefs.shakespeare=TRUE;