Am 14.12.2011 13:12, schrieb thron7:
>
> On 12/14/2011 12:51 PM, thron7 wrote:
>> On 12/14/2011 12:17 PM, Dietrich Streifert wrote:
>>> Meanwhile I "solved?!?!?" the exception by moving the declaration of the
>>> methods "extendClass" and "getKeys" up to qx.Bootstrap (starting on line
>>> 64) right before method "define". Down at
>>> qx.Bootstrap.define("qx.Bootstrap", I replaced the definitions of
>>> "extendClass" and "getKeys" with:
>>>
>>> extendClass : qx.Bootstrap.extendClass,
>>> getKeys : qx.Bootstrap.getKeys,
>>>
>>> Anyway: this is the stacktrace shown in Titanium Studio:
>>>
>>> qx.Bootstrap.define() [qx-oo-noopt.js:129]
>>> (anonymous function)() [qx-oo-noopt.js:200]
>>> (anonymous function)() [app.js:2]
>>>
>>> where qx-oo-noopt.js is loaded from app.js line 2.
> Ah, now I see clearer. If you look at the code in 'define' these
> delicate calls to extendClass and getKeys are guarded by checks for the
> passed-in defining map (config.members and config.extend). But the map
> passed in the qx.Bootstrap.define call (l.200) does not contain any of
> those, hence these paths are never taken (and shouldn't in this case).
>
> Could you check if there is a 'magic' "config" object hanging around on
> Titanium/Android?
>
> T.
>
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!!!
------------------------------------------------------------------------------
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
