Not using one class per file I problematic. It will break a lot of stuff e.g. things like the API viewer, the include sort system, the file tracer (to find out the name of a class and its requirements). I would say it by far easier to split files up than to support such things in our build system. It also makes it uglier at code level in my opinion.
Sebastian dperez schrieb: > 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 ------------------------------------------------------------------------- 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
