The more general approach that I expected would be to have at least 3 qooxdoo libraries: - one containing generic code, potentially used on various platforms - one containing platform-specific code used for the client - on containing platform-specific code used for the server
The latter two could both include the first, and in the client library you would generate a client-specific loader from all involved classes, and in the server library you would create a server-specific loader for all involved classes. T. On 04/24/2012 03:31 PM, totty wrote: > First of all thank you for the detailed response. > > I've been reflecting on how to do it and it seems a great idea to create a > single project for all the stuff but generate 2 separate loaders, as you > said, one for the client and one for the server. > > This seems the best option available right now, and it's good enough. > > thanks again ;) > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/Reusing-server-side-code-in-the-client-side-how-to-get-rid-of-the-require-in-nodejs-suggestion-tp7452919p7495892.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
