via Ajaxian:

Patrick Fitzgerald posted a nice screencast explaining how he diagnosed and fixed an IE memory leak in his tabifier library. He walks through using the free tool Process Explorer to watch IE’s memory grow with each page refresh. Read the rest of this entry »

via Ajaxian:

When debugging your Ajax (or other Javascript) applications, you can never have too much information. Sometimes, it helps to have things all laid out there before you can really see the issue at hand. This handy little script can help you get a better idea of what the Javascript on your page is really like.

The Javascript ObjectTree Favelet superimposes the current Javascript landscape of the page you’re viewing and is as simple as clicking a link and calling a function.

This will overlay your current document with a DIV element containing a collapsed list of all the javascript object types currently referenced by the page, from functions to strings to booleans and all else that falls between. Clicking the object type – for example “function”, will expand a new list with all of the function names. Clicking one of the function names will expand into the function’s body.

So, what’s the best part of the script, you ask? Well, maybe the fact that it’s not a script at all – it’s actually a bookmarklet, making it possible for you to use it on any page you visit. All you need to do is visit their page and all the link at the bottom to your toolbar or bookmarks list. It’s that easy.

This may be old news to some of you.

http://www.sitevista.com/

3 min. video tour: http://www.sitevista.com/demo.asp

Let’s you preview a rendered version of your site in just about any browers. It’s not an approximation, but an actual screenshot of your site as that browser processes it. It won’t let us see how our interactive elements work (javascript/ajax). Thoughts?

According to this post on the mir.aculou.us website, Justin Palmer has released event:Selectors, a “method to cleanly use CSS pseudo selectors to assign DOM events to elements on the page.”

The functionality, bearing resemblance to the behaviour.js library, hooks into all of the latest Prototype functionality and adds a few tricks of its own. They provide a code example of how this new functionality can be used:

var Rules = {
'#icons a:mouseover': function(element) {
var app = element.id;
new Effect.BlindDown(app + '-content',
{queue: 'end', duration: 0.2});
},'#icons a:mouseout': function(element) {
var app = element.id;
new Effect.BlindUp(app + '-content',
{queue: 'end', duration: 0.2});
}
}

I’m working on a little proof of concept project and started the task of writing a simple client-side template parser. After a few hours and some significant progress, I ran into a snag where the solution I had working just wasn’t as elegant as I wanted it. “What am I doing??” I asked myself. Ten seconds and one google search later I found Trimpath’s Javascript Templating library. Read the rest of this entry »