Hello David, > Hi, > > Is there a technical reason why the migration is only possible when I have > one class for one file?. > qooxdoo always had the concept of one class per file and for the python patch file, which transforms the old classes into the new class definition assumes exactly that. This file is the heart of the migration and I am reluctant to touch it so close before the final 0.7 release. I think some major rework has to be done there to support multiple classes per file. > As a Java programmer I think this is a good convention, and also for a > general purpose lib like qooxdoo, where each user selects what he wants, and > can create custom builds. > > But in my case, each javascript has exactly the classes I need, and won't be > used anywhere else. I avoid builds, can edit more easily as I see every use > of a variable/function/method by the highlighting of JSEclipse, and can > debug also easily. > > I would spend a lot of time to split into a lot of files just for migrating > (I have some very big javascripts of over 6000 lines and 40 classes or so, > mixed with plain functions). > For previous migrations, I just renamed qx.OO.defineClass to something else, > to fool the migration script, but this time it isn't possible. > > I foresee some more migrations. > Any workaround to splitting? > Thanks for any hint. > None that I know of but don't let you scare by the build system. It's not that complicated and it gives you plenty more features.
Best Fabian ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
