After a good read though Javascript: The Good Parts , and the start of a rather large class that I'll be writing in my spare time, I thought of how I could setup private variables in a Mootools class. YUI's Module pattern is an easy way to make some private variables, but it needed to fit into the Mootools Class pattern. So I merged the two ideas, and created a Class Mutator, that lets you define a Privates object, and you get private variables!
Yes, everything. All the fights, all the ugly words, all the bruises, all the broken keyboards, all the late nights. They were your fault, IE6. It feels rather liberating to be free of you. At least, personally. (Sometimes my boss makes me work with you, but its purely professional at those times.)
If you use a library that mimics classical inheritance into Javascript, like Prototype or Mootools, then you use the new Element() expression aplenty. It feels far nice to do it all in one constructor-like call, then using document.createElement , and then node.setAttribute and so forth a bunch of times. But I'm not going to argue which is more proper. Instead, what I've found is an annoying inconsistency with Internet Explorer 7 (probably 6 as well, but I didn't bother to check the obvious) when specifying the onclick attribute .
Apparently, Aaron Newton and Valerio have released a mooBugger bookmarklet that you can save at a bookmark in one of your other browsers (Internet Explorer, Safari, et al). This bookmark can then be clicked from any site, and it will load and run javascript on that page and build a close clone of Firebug .
