Migration Guide

Migrating from a previous qooxdoo version to a current release often requires nothing more than just running the migration job in your application. Yet, some changes between releases may involve manual modifications as detailed in the migration guide of each individual release. The following guide cover both cases.

If you are migrating from a legacy verison of qooxdoo to 1.6.1, namely from a 0.8.2 or prior release, please do a two-step migration to 1.6.1. Firstly, migrate to qooxdoo 0.8.3, following the instructions in the corresponding manual. You will need a qooxdoo 0.8.3 SDK to go through the process, so fetch one from the download location. This is necessary as there have been major changes in qooxdoo which require the infrastructure of the intermediate version to bridge. Then, follow the remaining steps in this document.

• Backup

  You might want to create a backup of your application files first. The migration process changes source files in place, modifying your code base.

• Configuration

  • Then, after you have unpacked the new qooxdoo SDK on your system, change references to it in your config.json and possibly in generate.py to point to the new version (look for "QOOXDOO_PATH"). Make sure that the path ends in the root directory of the SDK (like .../qooxdoo-1.6.1-sdk).
  • Check the current release notes and those of previous releases between your current version and 1.6.1 for changes to the generator configuration, as they have to be done by hand. Make sure you apply them to your config.json as far as they affect you. For example, with 0.8.1 the config.json macro QOOXDOO_PATH does not include the trailing "framework" part anymore, so make sure to add that in references to the qooxdoo class library. E.g. if you list the qooxdoo framework Manifest.json explicitly in your config using QOOXDOO_PATH, it should read ${QOOXDOO_PATH}/framework/Manifest.json.
  • Alternatively, particularly if you config.json is rather small, create a separate gui skeleton elsewhere and copy its config.json over to your application, and port the config settings from your old configuration to this file. This might be the simpler approach.

• Run Migration

  Then change to your application's top-level directory and invoke the command

  generate.py migration
  

• Follow the instructions of the migration script, particularly allow the cache to be deleted. For more information about this script, see the corresponding job description.

• Migration Log

  Check the migration.log which is created during the run of the migration script. Check all hints and deprecation warnings in the log and apply them to your code.

• Test

  You now have an up-to-date source tree in your application. Run

  generate.py source
  

  to check that the generation process goes through and test your application in the browser.