Jim,

did you find a way to get around Chrome's aggressive caching habits? I just
can't get Chrome to reload the Qooxdoo (source) code after changing
something in the source (short of exiting an restarting Chrome).

Cheers,
Fritz

On Sun, 7 Mar 2010, Jim Hunter wrote:

> I stand corrected. I am not getting my messages, only the JavaScript error
> message. But with FB 1.5 I wasn't even getting those. It looks like there is
> a problem with the FF/FB combo. Have you tried the new debug console in
> Chrome yet? I played with it and it is very similar to FB.
>
> I think I will go back and see if it works better then FB right now.
>
> Jim
>
> On Sun, Mar 7, 2010 at 9:37 AM, Qoodary <[email protected]> wrote:
>
>>
>> Hi Jim,
>> thanks for your help.
>> It is very strange. I first habe downgraded to FB 1.5.0 and same => no
>> debug
>> messages to see
>> Then I have upgraded to FF 3.6 and FB 1.5.2 and also the same :( nothing to
>> see in the console.
>> The network messages appears.
>>
>> I have no idea what I can do.
>>
>> best regards
>> Hansjoerg
>>
>>
>> Jim Hunter wrote:
>>>
>>> I had ver FF 3.6/FB 1.5  and was not getting messages either. I upgraded
>>> to
>>> FB 1.5.2 and I am now getting messes. What you might try, is to disable
>>> both
>>> the console and net and then re-enable them. That might give FB a shot in
>>> the arm to get them going again.
>>>
>>> Jim
>>>
>>>
>>> On Sun, Mar 7, 2010 at 8:48 AM, Qoodary <[email protected]> wrote:
>>>
>>>>
>>>> Hey Daniel,
>>>>
>>>> thank you very much for your help.
>>>> Yes I have enabled all.
>>>>
>>>>      if (qx.core.Variant.isSet("qx.debug", "on"))
>>>>      {
>>>>        // support native logging capabilities, e.g. Firebug for Firefox
>>>>        qx.log.appender.Native;
>>>>        // support additional cross-browser console. Press F7 to toggle
>>>> visibility
>>>>        qx.log.appender.Console;
>>>>      }
>>>>
>>>> The debugging was fine two weeks back. I am a little bit confused about
>>>> that
>>>> I cannot see no more messages in Firebug now. Is it possible that the
>>>> newer
>>>> Firebug version 1.5.2 is the problem?
>>>>
>>>> best regards
>>>> Hansjoerg
>>>>
>>>>
>>>> Daniel Hirtzbruch wrote:
>>>>>
>>>>>
>>>>> Hey Hansjoerg,
>>>>>
>>>>> are you sure you included the whole part to register firebug console
>> in
>>>>> your
>>>>> main application file %YourProjectDir%Application.js?
>>>>>
>>>>> [code]
>>>>>       // Enable logging in debug variant
>>>>>       if (qx.core.Variant.isSet("qx.debug", "on"))
>>>>>       {
>>>>>         // support native logging capabilities, e.g. Firebug for
>>>> Firefox
>>>>>         qx.log.appender.Native;
>>>>>         // support additional cross-browser console. Press F7 to
>> toggle
>>>>> visibility
>>>>>         qx.log.appender.Console;
>>>>>       }
>>>>> [/code]
>>>>>
>>>>> IMHO this should do the trick ;-)
>>>>>
>>>>> HTH, regards,
>>>>> Daniel
>>>>> --
>>>>> View this message in context:
>>>>>
>>>>
>> http://n2.nabble.com/No-debug-messages-in-Firebug-tp4686906p4687204.html
>>>>> Sent from the qooxdoo mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>
>> ------------------------------------------------------------------------------
>>>>> Download Intel&#174; Parallel Studio Eval
>>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>>> proactively, and fine-tune applications for parallel performance.
>>>>> See why Intel Parallel Studio got high marks during beta.
>>>>> http://p.sf.net/sfu/intel-sw-dev
>>>>> _______________________________________________
>>>>> qooxdoo-devel mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>>
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>>
>> http://old.nabble.com/No-debug-messages-in-Firebug--tp27805502p27812658.html
>>>> Sent from the qooxdoo-devel mailing list archive at Nabble.com.
>>>>
>>>>
>>>>
>>>>
>> ------------------------------------------------------------------------------
>>>> Download Intel&#174; Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> qooxdoo-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>>
>>>
>>>
>> ------------------------------------------------------------------------------
>>> Download Intel&#174; Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/No-debug-messages-in-Firebug--tp27805502p27813050.html
>> Sent from the qooxdoo-devel mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [email protected]
>> 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

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to