thank you!
Am 02.07.2008 um 07:27 schrieb Matthias Wessendorf:
On Wed, Jul 2, 2008 at 7:20 AM, Burghard Britzke
<[EMAIL PROTECTED]> wrote:
thank you. but is there any hint for searching (and finding) in the
firebug?
yes. Go to the script tab, select the Trinidad file, and do a search
at the very right.
Find the desired section highlighted in the content part of firebug.
I attached a screenshot to this mail as well
-Matthias
Am 02.07.2008 um 07:11 schrieb Matthias Wessendorf:
On Tue, Jul 1, 2008 at 9:13 PM, Burghard Britzke
<[EMAIL PROTECTED]> wrote:
ok! I tried it with firebug before but it is a little bit tricky
to find
the
right location for the breakpoint in a 30,000 lines code without
a search
funktion.
for debugging, I'd say this in my web.xml as well:
<context-param>
<param-name>org.apache.myfaces.trinidad.DEBUG_JAVASCRIPT</param-
name>
<param-value>true</param-value>
</context-param>
for production I'd avoid that, b/c when not present (and therefore
false)
we do
obfuscating, due to perf. reasons.
so my question is: does trinidad deliver the same script file for
every
request? because you told me that it is build out of many smaller
files.
yes, that is faster than serving 20 files.
And this file will be cached by the browser of your choice.
-M
sincerely,
burghard.
Am 01.07.2008 um 09:57 schrieb Matthias Wessendorf:
On Tue, Jul 1, 2008 <[EMAIL PROTECTED]> wrote:
is it possible to get some debugging info about what is going
on at the
client when pressing some link or button?
It seems that nearly every thing is coded in the
(Debug)Common1_2_8.js.
but
how to get info about infos about the state of its objects at
some
points?
This file is created out of several smaller files. And yes,
therefore
it has everything inside.
For debugging I'd do the following:
-Get Firebug
-check the HTML source what JS function is executed on the click
-find the func in the JS file, set a breakpoint
-do the click and debug through it
Greetings,
Matthias
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
<firebug_intro.PNG>
