qooxdoo

Build broken - How to debug?

Classic

List

Threaded

10 messages Options

Christof Rodejohann

Build broken - How to debug?

Hi,

i have been building quite a complex application in Qooxdoo. I have
been working in the "source-all" build and everything is working
great. Now i am closing in to a first iteration and tried the "build"
build. There are no errors in the generate process of the "source-all"
and "build". And no JS errors using the "source-all" app. But when
trying to use the "build" app it just stops working at an very early
event. I get no error to console or anything.

Can anyone give me a hint how to debug the "build" build?

Thx.
Christof

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Tristan Koch

Re: Build broken - How to debug?

Hi Christof,

try "source" first.

The "build" variant may catch and swallow errors depending on your configuration. Also, qx.debug is off by default. This does make sense for production, since you usually don't want to confront your users with error messages. But for debugging, you want to see all errors.

My (wild) guess is that you need to manually require a class using the #require annotation.

Regards
Tristan

Am 27.02.2012 um 11:28 schrieb Christof Rodejohann:

> Hi,
>
> i have been building quite a complex application in Qooxdoo. I have
> been working in the "source-all" build and everything is working
> great. Now i am closing in to a first iteration and tried the "build"
> build. There are no errors in the generate process of the "source-all"
> and "build". And no JS errors using the "source-all" app. But when
> trying to use the "build" app it just stops working at an very early
> event. I get no error to console or anything.
>
> Can anyone give me a hint how to debug the "build" build?
>
> Thx.
> Christof
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Christof Rodejohann

Re: Build broken - How to debug?

Hi,

"source" runs like a charm. No errors, warnings whatsoever. How do i
disable the catching of the errors in "build" to debug the current
error? What might be a situation where i am needed to manually require
a class which is loaded in "source" but not in "build"?

Regards
Christof

2012/2/27 Tristan Koch <[hidden email]>:

> Hi Christof,
>
> try "source" first.
>
> The "build" variant may catch and swallow errors depending on your configuration. Also, qx.debug is off by default. This does make sense for production, since you usually don't want to confront your users with error messages. But for debugging, you want to see all errors.
>
> My (wild) guess is that you need to manually require a class using the #require annotation.
>
> Regards
> Tristan
>
> Am 27.02.2012 um 11:28 schrieb Christof Rodejohann:
>
>> Hi,
>>
>> i have been building quite a complex application in Qooxdoo. I have
>> been working in the "source-all" build and everything is working
>> great. Now i am closing in to a first iteration and tried the "build"
>> build. There are no errors in the generate process of the "source-all"
>> and "build". And no JS errors using the "source-all" app. But when
>> trying to use the "build" app it just stops working at an very early
>> event. I get no error to console or anything.
>>
>> Can anyone give me a hint how to debug the "build" build?
>>
>> Thx.
>> Christof
>>
>> ------------------------------------------------------------------------------
>> Try before you buy = See our experts in action!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-dev2
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Christian Hagendorn

Re: Build broken - How to debug?

Administrator

In reply to this post by Christof Rodejohann

CONTENTS DELETED

The author has deleted this message.

fritz

Re: Build broken - How to debug?

Another difference between source and build version is that access to
private variables (starting with __) works in the source version, but
doesn't in the build version as the variable names are "optimized away".

You could disable the optimization steps in the build process (config.json,
it's described somewhere in the documentations).

Cheers,
Fritz

On Mon, 27 Feb 2012, hagendorn wrote:

> Hi Christof,
>
> could you please try to clean your artefacts with "generate.py distclean"
> and try to rebuild it with "generate.py source". Does the source version
> work?
>
> Cheers,
> Chris
>
> --
> View this message in context: http://qooxdoo.678.n2.nabble.com/Build-broken-How-to-debug-tp7321369p7321552.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>

--
Oetiker+Partner AG tel: +41 62 775 9903 (direct)
Fritz Zaucker +41 62 775 9900 (switch board)
Aarweg 15 +41 79 675 0630 (mobile)
CH-4600 Olten fax: +41 62 775 9905
Schweiz web: www.oetiker.ch

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
qooxdoo-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Tristan Koch

Re: Build broken - How to debug?

In reply to this post by Christof Rodejohann

Hi Christof,

so "source" works, but "build" does not. Well, generally this shouldn't happen. Let's dig a little deeper.

To enable debugging in the build variant, add this to your configuration ("jobs" section):

"build-script" :
{
"environment" :
{
"qx.debug" : true
}
}

One potential source of error might be code optimization. To turn off code optimization, define an empty OPTIMIZE macro, like this:

"let":
{
…
"OPTIMIZE" : []
}

A situation where you might need to manually require is when dependencies cannot be detected automatically, for example if you do some dynamic class resolution. However, the fact that "source" is working fine basically rules that kind of error out.

Hope this helps!

Tristan

Am 27.02.2012 um 11:58 schrieb Christof Rodejohann:

> Hi,
>
> "source" runs like a charm. No errors, warnings whatsoever. How do i
> disable the catching of the errors in "build" to debug the current
> error? What might be a situation where i am needed to manually require
> a class which is loaded in "source" but not in "build"?
>
> Regards
> Christof
>
>
> 2012/2/27 Tristan Koch <[hidden email]>:
>> Hi Christof,
>>
>> try "source" first.
>>
>> The "build" variant may catch and swallow errors depending on your configuration. Also, qx.debug is off by default. This does make sense for production, since you usually don't want to confront your users with error messages. But for debugging, you want to see all errors.
>>
>> My (wild) guess is that you need to manually require a class using the #require annotation.
>>
>> Regards
>> Tristan
>>
>> Am 27.02.2012 um 11:28 schrieb Christof Rodejohann:
>>
>>> Hi,
>>>
>>> i have been building quite a complex application in Qooxdoo. I have
>>> been working in the "source-all" build and everything is working
>>> great. Now i am closing in to a first iteration and tried the "build"
>>> build. There are no errors in the generate process of the "source-all"
>>> and "build". And no JS errors using the "source-all" app. But when
>>> trying to use the "build" app it just stops working at an very early
>>> event. I get no error to console or anything.
>>>
>>> Can anyone give me a hint how to debug the "build" build?
>>>
>>> Thx.
>>> Christof
>>>
>>> ------------------------------------------------------------------------------
>>> Try before you buy = See our experts in action!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-dev2
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Try before you buy = See our experts in action!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-dev2
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Christof Rodejohann

Re: Build broken - How to debug?

Hi,

thank you all for your help. It was like Fritz suggested the access to
a private variable. Child classes trying to access a private variable
defined in the parent class does not work in "build".

Also thx for the debug snippet. I am sure this will come in handy.

Regards
Christof

2012/2/27 Tristan Koch <[hidden email]>:

> Hi Christof,
>
> so "source" works, but "build" does not. Well, generally this shouldn't happen. Let's dig a little deeper.
>
> To enable debugging in the build variant, add this to your configuration ("jobs" section):
>
> "build-script" :
> {
> "environment" :
> {
> "qx.debug" : true
> }
> }
>
> One potential source of error might be code optimization. To turn off code optimization, define an empty OPTIMIZE macro, like this:
>
> "let":
> {
> …
> "OPTIMIZE" : []
> }
>
> A situation where you might need to manually require is when dependencies cannot be detected automatically, for example if you do some dynamic class resolution. However, the fact that "source" is working fine basically rules that kind of error out.
>
> Hope this helps!
>
> Tristan
>
> Am 27.02.2012 um 11:58 schrieb Christof Rodejohann:
>
>> Hi,
>>
>> "source" runs like a charm. No errors, warnings whatsoever. How do i
>> disable the catching of the errors in "build" to debug the current
>> error? What might be a situation where i am needed to manually require
>> a class which is loaded in "source" but not in "build"?
>>
>> Regards
>> Christof
>>
>>
>> 2012/2/27 Tristan Koch <[hidden email]>:
>>> Hi Christof,
>>>
>>> try "source" first.
>>>
>>> The "build" variant may catch and swallow errors depending on your configuration. Also, qx.debug is off by default. This does make sense for production, since you usually don't want to confront your users with error messages. But for debugging, you want to see all errors.
>>>
>>> My (wild) guess is that you need to manually require a class using the #require annotation.
>>>
>>> Regards
>>> Tristan
>>>
>>> Am 27.02.2012 um 11:28 schrieb Christof Rodejohann:
>>>
>>>> Hi,
>>>>
>>>> i have been building quite a complex application in Qooxdoo. I have
>>>> been working in the "source-all" build and everything is working
>>>> great. Now i am closing in to a first iteration and tried the "build"
>>>> build. There are no errors in the generate process of the "source-all"
>>>> and "build". And no JS errors using the "source-all" app. But when
>>>> trying to use the "build" app it just stops working at an very early
>>>> event. I get no error to console or anything.
>>>>
>>>> Can anyone give me a hint how to debug the "build" build?
>>>>
>>>> Thx.
>>>> Christof
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Try before you buy = See our experts in action!
>>>> The most comprehensive online learning library for Microsoft developers
>>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>>> http://p.sf.net/sfu/learndevnow-dev2
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Try before you buy = See our experts in action!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-dev2
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>> ------------------------------------------------------------------------------
>> Try before you buy = See our experts in action!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-dev2
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Marc Puts

Re: Build broken - How to debug?

Hi Christof,
Great to hear you found the problem.

But I'm puzzled... wouldn't accessing a non-existing object member cause
a javascript error in the console, even in the build version?

On 02/27/2012 02:30 PM, Christof Rodejohann wrote:

> Hi,
>
> thank you all for your help. It was like Fritz suggested the access to
> a private variable. Child classes trying to access a private variable
> defined in the parent class does not work in "build".
>
> Also thx for the debug snippet. I am sure this will come in handy.
>
> Regards
> Christof
>
> 2012/2/27 Tristan Koch<[hidden email]>:
>> Hi Christof,
>>
>> so "source" works, but "build" does not. Well, generally this shouldn't happen. Let's dig a little deeper.
>>
>> To enable debugging in the build variant, add this to your configuration ("jobs" section):
>>
>> "build-script" :
>> {
>> "environment" :
>> {
>> "qx.debug" : true
>> }
>> }
>>
>> One potential source of error might be code optimization. To turn off code optimization, define an empty OPTIMIZE macro, like this:
>>
>> "let":
>> {
>> …
>> "OPTIMIZE" : []
>> }
>>
>> A situation where you might need to manually require is when dependencies cannot be detected automatically, for example if you do some dynamic class resolution. However, the fact that "source" is working fine basically rules that kind of error out.
>>
>> Hope this helps!
>>
>> Tristan
>>
>> Am 27.02.2012 um 11:58 schrieb Christof Rodejohann:
>>
>>> Hi,
>>>
>>> "source" runs like a charm. No errors, warnings whatsoever. How do i
>>> disable the catching of the errors in "build" to debug the current
>>> error? What might be a situation where i am needed to manually require
>>> a class which is loaded in "source" but not in "build"?
>>>
>>> Regards
>>> Christof
>>>
>>>
>>> 2012/2/27 Tristan Koch<[hidden email]>:
>>>> Hi Christof,
>>>>
>>>> try "source" first.
>>>>
>>>> The "build" variant may catch and swallow errors depending on your configuration. Also, qx.debug is off by default. This does make sense for production, since you usually don't want to confront your users with error messages. But for debugging, you want to see all errors.
>>>>
>>>> My (wild) guess is that you need to manually require a class using the #require annotation.
>>>>
>>>> Regards
>>>> Tristan
>>>>
>>>> Am 27.02.2012 um 11:28 schrieb Christof Rodejohann:
>>>>
>>>>> Hi,
>>>>>
>>>>> i have been building quite a complex application in Qooxdoo. I have
>>>>> been working in the "source-all" build and everything is working
>>>>> great. Now i am closing in to a first iteration and tried the "build"
>>>>> build. There are no errors in the generate process of the "source-all"
>>>>> and "build". And no JS errors using the "source-all" app. But when
>>>>> trying to use the "build" app it just stops working at an very early
>>>>> event. I get no error to console or anything.
>>>>>
>>>>> Can anyone give me a hint how to debug the "build" build?
>>>>>
>>>>> Thx.
>>>>> Christof
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Try before you buy = See our experts in action!
>>>>> The most comprehensive online learning library for Microsoft developers
>>>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>>>> http://p.sf.net/sfu/learndevnow-dev2
>>>>> _______________________________________________
>>>>> qooxdoo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Try before you buy = See our experts in action!
>>>> The most comprehensive online learning library for Microsoft developers
>>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>>> http://p.sf.net/sfu/learndevnow-dev2
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>> ------------------------------------------------------------------------------
>>> Try before you buy = See our experts in action!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-dev2
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>> ------------------------------------------------------------------------------
>> Try before you buy = See our experts in action!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-dev2
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Thomas Herchenroeder

Re: Build broken - How to debug?

On 02/27/2012 02:42 PM, Marc Puts wrote:
> Hi Christof,
> Great to hear you found the problem.
>
> But I'm puzzled... wouldn't accessing a non-existing object member cause
> a javascript error in the console, even in the build version?

Exactly! And in the 'source' version you should have seen warnings about
that, didn't you?!

Which browser console are you using? Firebug? Chrome Developer Tools?

T.

>
> On 02/27/2012 02:30 PM, Christof Rodejohann wrote:
>> Hi,
>>
>> thank you all for your help. It was like Fritz suggested the access to
>> a private variable. Child classes trying to access a private variable
>> defined in the parent class does not work in "build".
>>
>> Also thx for the debug snippet. I am sure this will come in handy.
>>
>> Regards
>> Christof
>>
>> 2012/2/27 Tristan Koch<[hidden email]>:
>>> Hi Christof,
>>>
>>> so "source" works, but "build" does not. Well, generally this shouldn't happen. Let's dig a little deeper.
>>>
>>> To enable debugging in the build variant, add this to your configuration ("jobs" section):
>>>
>>> "build-script" :
>>> {
>>> "environment" :
>>> {
>>> "qx.debug" : true
>>> }
>>> }
>>>
>>> One potential source of error might be code optimization. To turn off code optimization, define an empty OPTIMIZE macro, like this:
>>>
>>> "let":
>>> {
>>> …
>>> "OPTIMIZE" : []
>>> }
>>>
>>> A situation where you might need to manually require is when dependencies cannot be detected automatically, for example if you do some dynamic class resolution. However, the fact that "source" is working fine basically rules that kind of error out.
>>>
>>> Hope this helps!
>>>
>>> Tristan
>>>
>>> Am 27.02.2012 um 11:58 schrieb Christof Rodejohann:
>>>
>>>> Hi,
>>>>
>>>> "source" runs like a charm. No errors, warnings whatsoever. How do i
>>>> disable the catching of the errors in "build" to debug the current
>>>> error? What might be a situation where i am needed to manually require
>>>> a class which is loaded in "source" but not in "build"?
>>>>
>>>> Regards
>>>> Christof
>>>>
>>>>
>>>> 2012/2/27 Tristan Koch<[hidden email]>:
>>>>> Hi Christof,
>>>>>
>>>>> try "source" first.
>>>>>
>>>>> The "build" variant may catch and swallow errors depending on your configuration. Also, qx.debug is off by default. This does make sense for production, since you usually don't want to confront your users with error messages. But for debugging, you want to see all errors.
>>>>>
>>>>> My (wild) guess is that you need to manually require a class using the #require annotation.
>>>>>
>>>>> Regards
>>>>> Tristan
>>>>>
>>>>> Am 27.02.2012 um 11:28 schrieb Christof Rodejohann:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> i have been building quite a complex application in Qooxdoo. I have
>>>>>> been working in the "source-all" build and everything is working
>>>>>> great. Now i am closing in to a first iteration and tried the "build"
>>>>>> build. There are no errors in the generate process of the "source-all"
>>>>>> and "build". And no JS errors using the "source-all" app. But when
>>>>>> trying to use the "build" app it just stops working at an very early
>>>>>> event. I get no error to console or anything.
>>>>>>
>>>>>> Can anyone give me a hint how to debug the "build" build?
>>>>>>
>>>>>> Thx.
>>>>>> Christof
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Try before you buy = See our experts in action!
>>>>>> The most comprehensive online learning library for Microsoft developers
>>>>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>>>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>>>>> http://p.sf.net/sfu/learndevnow-dev2
>>>>>> _______________________________________________
>>>>>> qooxdoo-devel mailing list
>>>>>> [hidden email]
>>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>> ------------------------------------------------------------------------------
>>>>> Try before you buy = See our experts in action!
>>>>> The most comprehensive online learning library for Microsoft developers
>>>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>>>> http://p.sf.net/sfu/learndevnow-dev2
>>>>> _______________________________________________
>>>>> qooxdoo-devel mailing list
>>>>> [hidden email]
>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>> ------------------------------------------------------------------------------
>>>> Try before you buy = See our experts in action!
>>>> The most comprehensive online learning library for Microsoft developers
>>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>>> http://p.sf.net/sfu/learndevnow-dev2
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> [hidden email]
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>> ------------------------------------------------------------------------------
>>> Try before you buy = See our experts in action!
>>> The most comprehensive online learning library for Microsoft developers
>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>>> Metro Style Apps, more. Free future releases when you subscribe now!
>>> http://p.sf.net/sfu/learndevnow-dev2
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [hidden email]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>> ------------------------------------------------------------------------------
>> Try before you buy = See our experts in action!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-dev2
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> qooxdoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>

Christof Rodejohann

Re: Build broken - How to debug?

Hi,

no, neither warnings in "source" or Javascript errors in "build"
happened. I am using Firebug but also tested Chrome Developer Tools.
Are these warnings a new thing in 1.6? I am still on 1.5.

Regards
Christof

2012/2/27 thron7 <[hidden email]>:

>
>
> On 02/27/2012 02:42 PM, Marc Puts wrote:
>> Hi Christof,
>> Great to hear you found the problem.
>>
>> But I'm puzzled... wouldn't accessing a non-existing object member cause
>> a javascript error in the console, even in the build version?
>
> Exactly! And in the 'source' version you should have seen warnings about
> that, didn't you?!
>
> Which browser console are you using? Firebug? Chrome Developer Tools?
>
> T.
>