On 11/05/2012 02:55 PM, p3k wrote: > fwolbring wrote >> Well, if you open the huge output file, you wll see that this file is >> allready shrinked and obfusecated. So all files needed by qooxdoo rpc >> class >> is in this file. Not more or less. > That’s a pity… Just from the API reference I think qooxdoo’s Rpc handling is > one of the best for JavaScript I have seen so far. > > It would be very nice to use (given that a few tests meet my expectations) > but not for the price of more than half a megabyte of JS code. > > I doubt that all the stuff in the output is really necessary, especially for > the Rpc class, and I hardly can imagine there is not a way to leave out all > the references to widget images, calendar data and the like…?
You're most probably right, but the Rpc class stems from a time when functionality was more the focus than efficiency (which is probably also true for a bunch of other classes). It's probably not a big issue to change the implementation in a way that would get rid of a lot of dependencies (e.g. making Rpc a 'qx.Boostrap.define' class), but then you probably would also need to take other qx.io.remote.* classes under scrutiny. But there are also other reasons to revamp the Rpc implementation [1]. Comments, votes and patches welcome. Unfortunately, there is so much work and only so little time... T. [1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=3975 ------------------------------------------------------------------------------ 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
