[Seaside] [Firebug] Programmatic halt
boris at deepcovelabs.com
Tue Jul 10 13:57:41 UTC 2007
Could you collect all your custom generated js from all components into a single 'file' at the time of page generation? I imagine that would solve the problem as well as make it easier on the browser.
(Sent from an iPhone... Not!)
----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: 'Seaside - general discussion' <seaside at lists.squeakfoundation.org>
Sent: Tue Jul 10 05:42:07 2007
Subject: RE: [Seaside] [Firebug] Programmatic halt
well Firegub is managing it like if they where inside an eval so
does not show the code as one expect to be shown. Thanks for the reference
The thing is that it works well when you make a classic js script in
a separate file with all the js code there. But the fact is that I'm using
js a lot more *smalltalkishly* than that. I install functions in js objects
defined at seaside components and that ends loaded up in the js objects fine
but in the sense of classic source code script "there is no script". I mean
there is one with minimal functionality (that I debug clasically) and the
rest is loaded "taylorly" from code found at attributes of the element's
wraper div. The installation of the functions is made just after the
homologous (to seaside component) js object is created.
I works like a charm, injects simplicity to smalltalk and js at once
(by injecting the smalltalk way in js) but it seems to be too much for
Firebug at debug time. I mean a smalltalk debugger in js will can you
> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> de Boris Popov
> Enviado el: Lunes, 09 de Julio de 2007 18:03
> Para: Seaside - general discussion
> Asunto: RE: [Seaside] [Firebug] Programmatic halt
> console.error("kind of like a breakpoint")
> It won't immediately bring up a breakpoint window, but you'll
> be able to click on a link and go straight to the bit of JS
> code where this was called.
> Hope this helps, see more over at,
> DeepCove Labs Ltd.
> 4th floor 595 Howe Street
> Vancouver, Canada V6C 2T5
> boris at deepcovelabs.com
> CONFIDENTIALITY NOTICE
> This email is intended only for the persons named in the
> message header. Unless otherwise indicated, it contains
> information that is private and confidential. If you have
> received it in error, please notify the sender and delete the
> entire message including any attachments.
> Thank you.
> > -----Original Message-----
> > From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> > bounces at lists.squeakfoundation.org] On Behalf Of Sebastian Sastre
> > Sent: Monday, July 09, 2007 12:31 PM
> > To: 'Seaside - general discussion'
> > Subject: [Seaside] [Firebug] Programmatic halt
> > Hi there,
> > anybody knows how to do a programmatic halt for js code
> so firebug
> > stops there?
> > I need that because I'm not defining all the js code in
> one script
> > "file" (which is actually a method in a FileLibrary) but kind of
> > fragmented. I'm making that because the definition of the
> behavior of
> > objecs is dynamic and "expectorated" from the seaside
> components. So I
> > will be unable to pre click (to set the red dot) a typical JS file
> line of
> > code as usually in firebug.
> > I saw that using "debugger" works for halting js code
> in IE. I'll
> > to use exacly something like that but in firebug. Is the js
> version of
> > beloved "self halt".
> > Anybody has a clue?
> > Thanks,
> > Sebastian Sastre
Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Seaside