Short: C= Installer 100% compatible replacement Author: jt18@irz.inf.tu-dresden.de (Jens Tröger) Uploader: jt18@irz.inf.tu-dresden.de (Jens Tröger) Version: 1.4 pre, Feb 8, 2000 Type: util/sys Distribution: Freeware InstallerNG is a 100% compatible replacement of the original C= Installer provided with the old OS 3.1 releases. InstallerNG is completly written from scratch with many new features and bugfixes where the old Installer is just a pitty. Additionally, it has a formal language definition, which is the reason for a stable compiler-kernel and the good interpreter. Also InstallerNG could be the new Installer in upcoming OS release (AmigaOS v3.6+) !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!! Please note that this is a PRERELEASE and not a final version !!! !!! It could have bugs where you adviced to report them to us. !!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Please take a look at it and have fun... Your InstallerNG Team, Jens Tröger Jens Langner Some of the new features are: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Nice GUI The builtin-gui is based on a BOOPSI class-collection, which was also written by Jens Tröger; these classes allow easy font-adaption, resizing and support MagicWB. Additionally, you may "plug-in" other gui-systems (like MUI, BGui, ...) via a shared library named "installergui.library". Furthermore, the help window can stay open, while you install your packages; this is a builtin feature and should be provided by every GUI - More strict interpretation InstallerNG is more compatible to the C= documented Installer script language. The original C= Installer v43+ isn`t really strict in interpreting scripts and many error are just ignored and not mentioned to the user. - Flexible interpretation If an error raises while the interpretation process, InstallerNG provides to continue at the very next function. - Interuptable Interpretation The InstallerNG can be interupted everytime by sending the CTRL-F signal to its process. This option allows to break out of infinite loops. - No restrictions The original installer has some terrible restrictions: maximum string-length, maximum size of a string value. The InstallerNG makes none of these: a string (and the value of a string variable too) can be as long as it fits into your memory. - Comfortable WB-Start If you run the InstallerNG from WB and give it no script via tooltypes a requester pops up which asks you whether you want to load a script by a file-requester or if you want to app-iconify the installer. If you drop a script-file on the application icon the InstallerNG gets started. - Returncode The InstallerNG now returns RETURN_OK (0) if everything of the installation went fine, or, in case of an error, it returns RETURN_FAIL (20). This could be useful, if you call the InstallerNG from a script and the script wants to check whether the InstallerNG was successfull or not. - SOOP - Simple Object Oriented Programing With help of the new functions PUT-PROPERTY, GET-PROPERTY and REMOVE-PROPERTY the InstallerNG implements LISP-like property-lists for symbols. Imagine of a symbol as an object and the properties as the objects attributes. Furthermore, if you write PROCEDURE`s, which are able to operate on an object`s attributes, you just can produce simple OO code :) ...without a class hierarchy, but object oriented! - UNDO-REDO environments Using the function "SWING" you are able to build an environment, in which you can "swing" from one (topmost) function to the next. When reaching the last one, the installation may proceed. This looks/works much like the MS-Setup program :) With v44 of the C= installer, you are able to simulate such an environment by special TRACE/RETRACE/BACK functions (have a look at the C= installer documentation) - Full installation control If you want to, the InstallerNG asks for confirmation of every action, no mattter what the script-programmer codes in his installer script - AppWindow InstallerNG can now act as an socalled "AppWindow", i.e. you may drop files into the window and InstallerNG uses them. This only works, when the InstallerNG asks for a file or directory. ... and many more ... please see the .guide file For more changes information, please read the .guide files attached in the archive.