Migrating from 1.4.1 to 2.1.1 should be straight forward. Switch the
QOOXDOO_PATH in your config.json to the new SDK and run 'generate.py
migration'. Go through all the messages in the migration.log and fix
potential issues. You should also go through all the intervening release
notes for changes you might need to apply manually. Then build your app
again with 'generate.py source'. Check your browser console during run
time for more bells and whistles.
T.
On 05/23/2013 05:47 PM, Jeroen Smit wrote:
Hi,
We are currently using Qooxdoo version 1.4.1 and I am trying to
investigate how much effort it would take to upgrade to the latest
greatest version.
Is there still some overview of steps to take and/or update scripts to
run (I can remember using them to upgrade from 0.7.3 to 1.4.1 but I
cannot find them online).
Thanks for any help in advance.
Best regards,
Jeroen
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
