The reception for our latest script release, jsTrace, has been fantastic. From the write-up on the DOM Scripting Task Force blog to all of the emails and comments, it’s been great.
The past few days have seen many ideas, requests and enhancements sent my way. Some have been rolled into the jsTrace 1.1 release which I made public today. One such enhancement (brought to us by Joe Shelby) I have dubbed “memory,” as it allows the debugging window to remember both its position and size the next time it is opened (via cookies). Further enhancements have been made to the underlying code to streamline development of additional tools for the bottom toolbar and the font size of the bottom toolbar has also been increased (per several requests).
I hope you all enjoy the improvements. Keep ‘em coming.
Update: We’ve also been mentioned in DOMScripting.com.
Another update (to 1.2): I added a buffer to handle traces executed prior to the jsTrace window being generated. The buffer is written to the viewport once it is generated.
Comments
Aaron, forgive me if someone has suggested this elsewhere. This is a very handy utility. I usualy output messages to a debug string and write it out at the end of a page … but obviously that’s no good for capturing events after the page has loaded. Anyway, a simple suggestion - once you’ve clicked so many times, the ‘alerts’ appear off the tracer panel. So, could you either a) auto scroll to show the latest alert/trace or b) provide an option (checkbox) to display most recent alert at the top.
Fine use of unobtrusive scripting sir!
Thanks Ian. It’s funny you should mention that as Dave & I were discussing that very feature yesterday. I will be posting a newly revised version which either a) tracks down with the newly traced lines or b) reverses the output direction in the coming days.
We have a few other improvements in queue too. I will post more when they are complete.