[qooxdoo-devel] Migration and 1 class per file.
Brought to you by:
ecker,
martinwittemann
From: dperez <cra...@ya...> - 2007-05-31 15:37:21
|
Hi, Is there a technical reason why the migration is only possible when I have one class for one 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. Regards David -- View this message in context: http://www.nabble.com/Migration-and-1-class-per-file.-tf3847245.html#a10896395 Sent from the qooxdoo-devel mailing list archive at Nabble.com. |