Hello Christian, > much more readable now!
Totally agree! Thats really looking good, but still I have to get used to see qooxdoo code run on a server. :) > What I had to do to make this work is to add "exports.qx = qx;" at > the end of the qx-oo.js file. Is that something that could be added to the > file by default? Or a special job "build-qx-oo-node-js"? But maybe this can > be solved differently. How did you import qx-oo as a module in node.js? I just used the require statement and did not assign the return value of it to qx. As the qx-oo script defines a global qx variable, it is not necessary to assign it. But the way you used it is more the way it would be used in node so I simply check how to include it in the loader template... shouldn't be a problem. Regards, Martin ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
