>> I've found that reverting all of the ".legacy." names to the originals >> seems to fix most of the problems.... my app appears to be back to >> where it was before I started migration, and seems to be working OK, >> or at least as well as it was before... >> > > Great. Meanwhile, I checked the migration data, and there is indeed a > migration step rewriting qx.ui -> qx.legacy.ui. But this of course only > affects code that is migrated from *0.7.x*, not 0.8.x! During migration, > you have to enter your current qooxdoo version, and the default is > 0.7.3, so if you just hit enter at this point, things can go astray... >
Actually, if this was the case with you, you might want to consider reverting to a version before the migration, and then re-run the migration, making sure you enter 0.8.2 as your current qooxdoo version. I don't know which kind of subtle bugs might get introduced by running migration procedures on code that is actually more current than the procedure assumes. T. > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
