dperez <[EMAIL PROTECTED]> writes: > Thanks for your explanation. > It could be that. I have all classes and functions into a big .js file. > But the migration tool cannot force me to that organization. > Do I have to split my .js file into a bunch of small .js in order to migrate > it? > In that case I prefer to do the migration manually.
There may be a switch you can use to disable the checks for directory hierarchy matching class hierarchy. You're now out of my area of knowledge, though. If you can do a manual migration reasonably easily, you may just want to do that. Otherwise, wait for a response from one of the people working on the migration tool (Andreas and Sebastian, I think). Although having the class hierarchy match the directory hierarchy is really nice within qooxdoo and I use it for my application hierarchy (now based on the new skeleton) as well, I agree it doesn't seem appropriate for the qooxdoo tools to be forcing that hierarchy on applications. I suspect there's some way around it. Cheers, Derrell ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
