Am 31.08.2011 14:34, schrieb thron7:
>
>
> On 08/31/2011 01:41 PM, Marcel Ruff wrote:
>> Am 30.08.2011 23:44, schrieb Derrell Lipman:
>>> I haven't been following the whole conversation, but this sort of problem
>>> is typically from use
>>> of a private variable someplace. See what happens if you turn off
>>> optimization for your build
>>> version. In the "let" section of config.json, add the following line:
>>>
>>> OPTIMIZE : [ ]
>>>
>>> which should disable all optimization. Then run "generate.py build" again.
>>> If nothing else, the
>>> variable i will likely be replaced with its original name, to hopefully
>>> guide you towards the
>>> culprit.
>> Thanks for the hint.
>>
>> Unfortunately the "generate.py build" stops after some processing with:
>>
>> Generate packages 'unicode' object has no attribute 'sort'
>
> Marcel, for one thing I can only guess how you incorporated Derrell's hint
> into your config.json,
> but from the error I guess you put it in the wrong place. Please read up in
> the manual about the
> global "let" macros.
>
> Derrells hint is not bad, and you might continue with it. But I wouldn't
> expect too much of it, as
> you already reported that "i" is recognized as a proper Document object (so I
> don't think the
> optimization has messed up). And there is no way even FF6 does away with
> Document.body :).
>
> So the only thinkable problem would be one of timing, as mentioned before,
> when the Document.body
> element is not yet ready. You should be able to extract that from the stack
> trace you are getting.
> Can you?
Thanks for taking care.
I will double check everything again and come back with my new insights,
regards
>
>>
>> Removing the OPTIMIZE:[] again, generate runs through but with the old error
>> "i.body is null"
>
> We've been through that before, and I guess you have to dig harder to find
> the cause of the error.
> If you are right and this is still the old error, this is perfectly innocent
> code from
> qx.bom.Viewport#getWidth, which runs fine for all other people. I've checked
> various of our
> standard applications which use qx.bom.Viewport in Firefox6, and they run
> flawlessly. The
> implementation of qx.bom.Viewport#getWidth hasn't changed since way before
> the 1.4 release, so
> there is no reason to believe this particular line of code is the root cause.
>
> How is your app doing in other browsers? What do you get in FF6 when you run
> our standard apps,
> e.g. Demobrowser~bom.Viewport, Showcase or Widgetbrowser?
>
>> Using "generate.py source" again the app runs perfectly.
>
> Ok, so that's a good thing to know, provided you are not also gettting
> warnings in the Firebug
> console. If you are experiencing a timing issue it takes no wonde ther source
> version is
> unaffected, as it loads slower than the build.
>
> T.
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
