> I'm out of ideas, so i'll copy the whole class (2400 lines of code) and pray
> that the updates don't change it too much
I would recommend to use the 'patch' feature if you only have to change one
ore two methods.
If you do a version check before you will at least get informed to check the
update (at runtime that is)
Something like this example:
----------------------------------------------------------
// Check whether we patch the correct framework version
if (qx.core.Environment.get("qx.version") !== "3.0.1") {
throw new Error("New framework version! Check patches!");
}
// Patch #1: RPC Queues
qx.Class.patch(qx.io.remote.RequestQueue,
qx.Mixin.define("infodesk.patch.RequestQueue",
{
members :
{
getActiveQueueLevel : function () {
return this.getActiveQueue().length;
},
isActiveQueueEmpty : function () {
return this.getActiveQueue().length === 0;
},
isActiveQueueFull : function () {
return this.getActiveQueue().length >=
this.getMaxConcurrentRequests();
}
}
})
);
// Patch #2: Whatever...
----------------------------------------------------------------
/Peter
--
*************************************************************
Besuchen Sie uns:
01.-03.10.2013 Post-Expo in Wien
Wir laden Sie herzlich ein und freuen uns auf Ihre Anmeldung.
*************************************************************
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
