All right, the problem is caused by your include list, specifically this 
entry:

"qx.*"

This causes all qx class code to be loaded and evaluated *before* the 
DOM is ready. Several qx classes have "defer" functions that are called 
as soon as the class is defined, and some of them, including qx.bom.Vml, 
will try to add elements to the DOM, causing the exception you're seeing.

So the question is, why are you including the entire framework in your 
"build" job? You really should leave it up to the Generator to sort out 
your dependencies, and use #require hints for the rare cases where it 
can't recognize a dependency.

On 07/31/2012 10:33 AM, totty wrote:
> *All the code is here:*
> https://github.com/totty90/production01_server/tree/master/node_modules/production/client/production
>
> *Now without any optimization the error persists and the line is this:*
> ,getVml:function(){var
> bv=document.createElement(b);document.body.appendChild(bv);bv.innerHTML=D;bv.firstChild.style.behavior=bl;var
> bw=typeof bv.firstChild.adj==s;document.body.removeChild(bv);return bw;}
>
> *Error:*
> Uncaught TypeError: Cannot call method 'appendChild' of null
> production.js:3294
>
> *Configuration:*
>       ,"build" :
>       {
>                "include": [
>                       "${APPLICATION}.*",
>                       "qx.*"
>               ]
>               ,"exclude": [
>                       "qx.test.*",
>                       "${APPLICATION}.test.*",
>                       "${APPLICATION}.simulation.*"
>               ]
>               ,"compile-options": {
>                       "code" :{
>                                "format": true
>                               ,"optimize": []
>                       }
>               }
>       }
>
>
> Yes, it seems to be the getVml:
>
> But how I do what you said?
>
>>> In a widget context, this sort of problem is usually solved by wrapping
>>> the code that calls appendChild in an "appear" listener to make sure it
> i>>isn't executed until the widget's DOM elements are created.
>
>
>
> --
> View this message in context: 
> http://qooxdoo.678.n2.nabble.com/Application-doesn-t-work-when-I-build-I-can-t-figure-out-what-is-the-problem-tp7580829p7580838.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to