thron7-2 wrote > If you insist on a stand-alone file you have to create one yourself. > Basically, you create a skeleton, configure qx.ui.remote.Rpc to be the > sole "include" member and run the 'build' job.
Well, I think I did that and the result is a huge JS file… (please see my previous post) thron7-2 wrote > [...] you just use the Rpc class in your code. [...] You are creating > a taylor-made library with every generator run, rather than dealing with > a static one. More than 650 KB of JS code for one specific aspect is not really what I imagine taylor-made; it rather would meet my definition of “whole qooxdoo framework”. ;) thron7-2 wrote > But is it really important to have an individual file, just to provide > the Rpc class? From my point of view it is because all I want is to add qooxdoo’s RPC capabilities to a project that does not need the other features of this framework – as excellent as these might be (and I guess they are). Cheers, tobi -- View this message in context: http://qooxdoo.678.n2.nabble.com/Which-package-is-needed-for-using-the-qx-io-remote-Rpc-prototype-tp7581873p7581903.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
