Hi Christian,
if you take the newest download version, you will have the
qx = require('./qx-oo')
syntax. Thats what I prefer. :)
Regards,
Martin
Am 09.08.2010 um 20:46 schrieb panyasan:
>
> Hi Martin,
>
>
> MartinWittemann wrote:
>>
>>> 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.
>>
>
> but I still wonder - should it be:
>
> qx = require('./qx-oo').qx;
>
> or rather:
>
> qx = require('./qx-oo');
>
> The first needs "exports.qx = qx", the second "exports = qx;". I like the
> second option better, but the node.js dev's councel against replacing the
> "exports" variable entirely with a custom object.
>
> C.
> --
> View this message in context:
> http://qooxdoo.678.n2.nabble.com/node-js-and-qooxdoo-tp5345772p5390139.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> 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
------------------------------------------------------------------------------
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
