> Yes, you are right. I updated the code. See attachment...
>
> window.log = {};
>
> /**
> * An appender that writes all messages to a log window.
This has now been included in the snippets - see
http://qooxdoo.oss.schlund.de/snippets/showing-debug-information
I put the code in a file which i
> > I tried this locally, but it only put a newline after each function
> > which makes it difficult to set breakpoints within a function. Any
> > hints on how to preserve every newline?
>
> Did you call make-clean.sh before make.sh?
Ah, that was it. I've updated the snippet as well.
Hugh
---
Now in the snippets at
http://qooxdoo.oss.schlund.de/snippets/newlines-in-build-files
Thanks.
I tried this locally, but it only put a newline after each function
which makes it difficult to set breakpoints within a function. Any hints
on how to preserve every newline?
Functions should look
> Normally all newlines in the compiled qooxdoo.js are removed. This
> makes it difficult to debug the qooxdoo code, since you get a stack
> trace that points always to the same single line.
Now in the snippets at
http://qooxdoo.oss.schlund.de/snippets/newlines-in-build-files
I tried this loca
Tilman Schneider schrieb:
The only problem is, that the whole code in qooxdoo.js is in one line.
So I changed my local version to have a newline after each semicolon.
This way I get real stack traces in the qooxdoo code, too.
Normally all newlines in the compiled qooxdoo.js are removed. This m
this is great work! well done.
Kent
On Wed, 2006-02-22 at 14:58 +, Hugh Gibson wrote:
> > You could either add a div to your page that has the id "demoDebug".
> > Then you have to include the demolayout.css, in order to get the
> > messages styled correctly.
>
> I've put this on the qooxdo
> You could either add a div to your page that has the id "demoDebug".
> Then you have to include the demolayout.css, in order to get the
> messages styled correctly.
I've put this on the qooxdoo snippets pages as
http://qooxdoo.oss.schlund.de/snippets/showing-debug-information
Hugh
If you change QxApplication.js, line 168 from
return this.error("...failed: " + ex);
to
return this.error("...failed: " + ex, ex);
then you'll get a stack trace to initialization errors in Firefox.
Example:
- snip -
ERROR: QxApplication: ...failed:this._weekdayLabelArr[i] has
Tilman Schneider schrieb:
What's about a patch to QxDebug, using probably a new QxSettings flag,
to toggle between a new window to show the debug messages and the
current solution? Something more qooxdoo'ish would be great ;)
Yes, of corse. This was just a quick hack to get logging into a wind
What's about a patch to QxDebug, using probably a new QxSettings flag,
to toggle between a new window to show the debug messages and the
current solution? Something more qooxdoo'ish would be great ;)
Yes, of corse. This was just a quick hack to get logging into a window
working.
We planned alr
Dietrich Streifert wrote:
btw.: I think one path points to your internal development class
hierarchie at:
onunload="com.ptvag.webcomponent.common.log.WindowAppender.getAppender
The prefix "com.ptvag.webcomponent.common." should be removed.
Yes, you are right. I updated the code. See attachme
Tilman Schneider schrieb:
Sorry guys for all these questions by a newbie...
How do I get the debug console running inside my application, ie what
must I do to see my this.debug messages printing ?
You could either add a div to your page that has the id "demoDebug".
Then you have to include th
Hi Tilman,
Thanks a lot for the great work and precious help !
Bye,
Laurent.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Tilman
Schneider
Envoyé : mardi 21 février 2006 17:10
À : qooxdoo-devel@lists.sourceforge.net
Objet : Re: [qooxdoo-devel]
Can you please send your mail again and rename the file to WindowLogger.j_
because outlook has blocked your atachement
see attachement...
window.log = {};
/**
* An appender that writes all messages to a log window.
*
* @param name {string,"Log"} the name of the log window.
* @param useTextA
Hi Tilman!
Great work!
Thanks allot!
btw.: I think one path points to your internal development class
hierarchie at:
onunload="com.ptvag.webcomponent.common.log.WindowAppender.getAppender
The prefix "com.ptvag.webcomponent.common." should be removed.
Is this OK?
Maybe this should be cont
Sorry guys for all these questions by a newbie...
How do I get the debug console running inside my application, ie what
must I do to see my this.debug messages printing ?
You could either add a div to your page that has the id "demoDebug".
Then you have to include the demolayout.css, in order
Sorry, I don't understand you.I mean, that is usefull to have a funtion "inspect" (like the debug one, or info). This function can show (in the debug console) the "state" of an object (attribute = value) and will be implemented as a function of QxObject.
What do you mean with "you are using program
And ... It could be possible to have an "inspect" function to show all the attributes of a qooxdoo object?Thanks ;)On 2/21/06, Oliver Vogel
<[EMAIL PROTECTED]> wrote:
sorry, this is not a answer, this is a feature request
;-)
it should be possible to have the debug-console in a
separate wind
18 matches
Mail list logo
