John J Barton wrote: > Our paper on breakpoints and a link to the demo page: > http://blog.getfirebug.com/2009/11/03/dynamic-and-graphical-web-page-breakpoints/
I'm truly impressed. I've been working with FF3.0.x and FB 1.4x; this is enough to make me upgrade to FF3.5 to get the new features. One enhancement occurs to me: IIUC, some of the new breakpoints can't be set until after an error occurs, or after an XHR has completed, etc., implying that the page must be reloaded to cause the breakpoints to be hit. I can imagine situations where this might be at least bothersome. For example, perhaps the operation so far has resulted in a database change that will cause the next reload to take a different execution path; in this case, it'll take some time to restore the context to ensure that the same condition will recur, and in extemis, might involve restarting the browser. Or, perhaps it's late in the day, and I'm getting tired, and a mysterious problem arises; I don't have time to pursue it, but I'd like to set the breakpoints before I shut down and have them set tomorrow morning when I start from fresh. My suggestion would be to offer a button or menu item to script out the current breakpoint set to a file, maybe in XML or JSON format, and a complementary one to load the file to set the breakpoints. If the format isn't too arcane, the user might be able to edit the file to change or create new breakpoints. FWIW, -- Don Dwiggins Advanced Publishing Technology -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
