Hi Balage,
I think the "magic" is in the following lines of code that are generated by
the template creation tool create-application.py
// 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;
}
The if statement enables debugging only for the source-version (or disables
it for the build-version) and the last line makes sure that there is a place
to go for the messages if your are not running a browser with built-in
console support.
Cheers,
Fritz
On Wed, 9 Dec 2009, [email protected] wrote:
> Hi everyone!
>
> I have a quite silly question: I tried to figure out, how the logging system
> works.
> I found the methods debug, info, warning and error of the Object, and the
> console.log function.
> The later seems to work only with Firefox and Firebug, but having a
> console.log call in the source makes the application to throw exception when
> opening from other browsers.
> OTOH, I wasn't able to find whrere it goes and how I could get the results
> produced by Object methods.
>
> I tried to find info, but starting to realize, that many of the documentation
> (called "Manual") of Qooxdoo is rather a very high level summary of the
> features than a manual.
>
> Thank you!
>
> Balage
--
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
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
