Am 14.12.2011 15:16, schrieb Dietrich Streifert:
> Back from my lunch break:
>
> I've startet a debugger session in Titanium Studio and set a
> breakpoint at line 3 of qx-oo-noopt.js which is the first instruction
> allowing to do so. Now I've been stepping through the code while
> evaluating "config", "config.members" and "config.extend" in the
> expressions window.
>
> config is still not defined until stepping into line 113 of
> qx-oo-noopt.js where it becomes defined in the current context because
> it is passed as parameter #2 to define in
>
> qx.Bootstrap.define("qx.Bootstrap",
> {
> statics : .....
>
> At this line config.members is not defined as expected, but
> config.extend IS DEFINED and holds a function reference.
>
> From my undestanding of the qx-oo bootstrap code config.extend should
> be undefined at this point.
>
> A simple evaluation of
>
> (new Object).extend
>
> shows that extend is a function reference.
>
> So I've restarted the debugger and found that Object.extend is defined
> by default before qx-oo is loaded.
>
> Umpfff!!!
>
This may be a valid solution for the problem: I've simply NULL-ed out
extend in qx.Bootstrap.define this way:
qx.Bootstrap.define("qx.Bootstrap",
{
extend : null,
statics :
{
.....
I don't know if this has any side effects.
------------------------------------------------------------------------------
Cloud Computing - Latest Buzzword or a Glimpse of the Future?
This paper surveys cloud computing today: What are the benefits?
Why are businesses embracing it? What are its payoffs and pitfalls?
http://www.accelacomm.com/jaw/sdnl/114/51425149/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
