> > qx.OO.defineClass changed to qx.Class.define with 0.7. According to > > your statement above, you're skipping the 0.7 migration. > > I'm skipping it in so far as that I'm not explicitly migrating to 0.7 > using the 0.7 SDK. I am running the 0.7 migrations included with 0.8 > though.
Which should actually suffice. I cannot remember much of the transition from 0.6.x to 0.7, but as Derrell said 0.7 introduced a new class factory, along with the class definition in a "closed form", i.e. capturing all class features in a single map (IIRC). > I have had a look at the migration files and can't find anything that > looks like it might migrate the class definitions - it's mostly just > regular expression replacements, and it doesn't look like that would be > enough for this. I had a look myself, and the transformation of the class factory was in fact not done by a regular expression, but by a syntax tree transformation (probably due to not only changing the factory functor but also the whole structure of the class file). But all those data is still there (the AST transformation is done by a patch.py script in the 0.7-beta1 migration data), and the migration driver still honors those patch.py files. So your intuition was completely right to expect an automatic migration of the class factory calls as well. I don't know what went wrong. I presume you faithfully reported 0.6.6 as your starting version when migrating to 0.8.3. Please have a look at the migration log, if there was any difficulty in going through the migration steps 0.6.6 -> 0.8.3. > It's also worth noting that in terms of the migration guides, the 1.3 > guide sends you to the 0.8 guide (for a migration starting with 0.6), > but the 0.8 guide does not mention 0.6 at all - it only refers to > upgrading from 0.7. :-) Well, 1.3 just talks about "prior versions" in a sort of hand-waving sense, while the 0.8 guide mentions 0.7 explicitly. I doubt, though, that a lot of consideration (or even testing!) was spent on 0.6 in either case. > > So maybe I should indeed try an explicit 0.7 migration, as in 0.6.6 -> > 0.7 -> 0.8 -> 1.3. Again, I would be interested if there were any perceivable issues in the direct 0.6.6 -> 0.8.3 migration (theory says, it should work :). Otherwise, doing 0.6.6 -> 0.7.x first should be a safe bet. T. ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
