HalogenWare

Banner

GlassWorks Updates

  • 1.2(Released 23rd-Nov-2009)
  • Changed installer behaviour so that newer files will never be overwritten during an installation.

  • 1.1(Released 13th-Jul-2009)
  • Links will now have their working directory set to be the target's directory (if supported).
  • Improved look and feel functionality
  • Links created on Linux and Unix based systems will now be marked as executable.

  • 1.09(Released 10th-Apr-2009)
  • Fixed bug on Linux where shortcuts could not be started if application was installed in a path with spaces.

  • 1.08(Released 28th-Oct-2008)
  • Fixed some cosmetic issues.

  • 1.07(Released 25th-Sep-2008)
  • Fixed hang during uninstall (Thanks to Stefan Meier).
  • Changed the way GlassWorks is run for Java 5 compatability.
  • Desktop integration on linux now uses a shell script for launching jar files.
  • Fixed regression on Macintosh OSX where application bundles were not deleted during uninstall.

  • 1.06(Released 21st-Jul-2008)
  • Files can now be marked individually for delete on restart.
  • Updated to use Tango icons as the default icon set.
  • You can now specify arguments to be passed to the launcher application for link, association or startup items.
  • Fixed issue where some empty directories were not being deleted on uninstall.

  • 1.05(Released 14th-Mar-2008)
  • Fixed bug in shared file counting.
  • Added capability to delete application created data files during uninstall.
  • Better integration with Macintosh OSX.
  • Added privilege elevation request for Windows Vista.
  • Added option to extract a file before executing commands.
  • Changed location for storing data files to be platform dependent.
  • Fixed bug in IcnWriter that created empty icons.
  • The output filename for the installer can now be specified.

  • 1.04(Released 17th-Dec-2007)
  • Fixed bug in Java version check that prevented the GlassWorks installer from running.
  • Improved reliability of deleting in use files after restart on Windows.
  • Fixed many internationalization issues when running the installers on non-english Windows systems. Special thanks to Stefan Meier and Igor A. Kondrashkin for all their feedback and testing.
  • Added option to install files with a different name from the original.
  • Added better control over launching deployed applications.
  • Integration options (links, associations, startup) can now be restricted by operating system.
  • Added some more command line options for installer generation.

  • 1.03(Released 2nd-July-2007)
  • Fixed regression where menu links were not created on Linux systems if installation was performed for current user only.
  • Fixed bug where the generated installer would not launch because of problem with custom stages.

  • 1.02(Released 10th-Apr-2007)
  • Installer applications will now accept the following command line options:
    • -silent, install the application using default settings or settings from a previous installation, no gui is displayed.
    • -headless, install the application using a command line interface instead of a graphical one.
    • path to config file, by copying the installation script (a file named gwscript) from one installation to another system and passing it's path as a command line argument the installation will automatically proceed using the script's stored values.
  • Setup applications will now accept the following command line options:
    • -uninstall, uninstall the application without displaying a gui.
    • -headless, run the setup application using a command line interface instead of a graphical one.
  • Fixed a bug in the installers where selecting context menu only for file type associations had no effect.
  • A description can now be added for installation groups.
  • Operating system specific groups can now be marked as required or optional.
  • Improved accuracy of disk space required estimation.

  • 1.01(Released 30th-Jan-2007)
  • Added quotes around jar open commands.
  • Expanded api to make customization easier and more powerful.
  • Fixed a bug in the produced installers where the application could not be reinstalled or upgraded if installation information written by a previous installation had been damaged.
  • Fixed issue on Windows systems where application would always be installed into "C:\Program Files" instead of using the proper applications folder.