[Seaside] Firebug ans JS generated with seaside

[Rick Flower]

On Fri, May 25, 2007 2:26 pm, Sebastian Sastre wrote:
>>
>> I *think* that Seaside does that to save space & transmission
>> time (a form of optimization).. If you're using Firebug, you
>> shouldn't have any problems viewing the page source easily
>> and nicely formatted at that.
>
> Yes Rick, but the point is I'm wanting more than just see code. I want to
> be
> able to debug and the HTML tree is pretty printed but some kind of useless
> to debug javascript.
>
> That's where the de-monolithication technique proposed by Martial B.
> enters
> in the scene,

Hmm.. I was able to debug my Seaside app's JS code (in this case YUI code)
using firebug OK.. I had to set a breakpoint (don't recall now how I did
that), but it would stop OK and I could inspect variables,etc...  I think
you will need to hit the "script" button near the top of the firebug
window and select the script you're interested in and then put a
breakpoint in the code to be debugged.  If you then re-load the page it
will remember the breakpoint and it will trigger next time the code is
executed.. At least it did for me.