For plugin developers like myself, it’s a pain in the @!+ as I’m now seeing users run into this problem on a daily basis for a few weeks now, and it has become obvious that the problem in every case is the forced loading of jQuery library files from CDNs, particularly Google.
The aim of loading jQuery libraries from external sources is to speed up page loading time, so no wonder why theme makers jump at this quick speed upgrade.
However, whilst there’s nothing wrong with doing this theoretically, they way they’re going about it couldn’t be more wrong! The various misleading posts circulating the web are most likely the cause of such a widespread problem, and now we’re starting to see the consequences as time passes.
When coding in mootools, a lot of function binding goes on in my case. In fact, pretty much every time I call a class method I want it bound to the class. Jan Kassens comes to the rescue with a simple method which enables your class functions to be bound upon initialization. If you find yourself using .bind(this) a lot, this could make your code much prettier.
Samuel Birch created a great image menu which can be found here at Phatfusion. I was upgrading some bits on a site for the lovely Mootools 1.2 release and as a result I had to make a small change to get imagemenu to work.
For those pages with loads of text a table of contents would be nice, with anchors located in relevant sections. Thing is that going through a page with thousands of words and headings is no fun at all.
I made a script using the lovely MooTools that gets all the elements with a given CSS selector (using the Elements.Selectors syntax) and then builds an unordered list of links, with the element text as the title, and an anchor placed in that element.