OK, thanks for your answer. I will split the files, migrate and merge back.
Sebastian Werner wrote: > > 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. > -- View this message in context: http://www.nabble.com/Migration-and-1-class-per-file.-tf3847245.html#a10964606 Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- 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
