There are many functionalities on the web that were just begging to be AJAXified. Whether it be voting on a poll or simply commenting on a blog post, there's really no reason to reload an entire page for something so simple. This blog has featured AJAX comments in WordPress for years, but only recently did I find the most optimized way to process those comments. Here's how to handle the WordPress PHP side of AJAX comment systems.Read Post
I've had the honor of writing for this year's PHP Advent, blessing you all about Cross-Origin Requests with CORS...Read Post
I've spent the last two weeks in London, eating fish'n'chips, drinking cup'o'tea, and being a hooligan at the Arsenal. Oh yeah, there was a MooTools hackathon too. The MooTools hackathon was hugely successful and I'll be providing more detail about what was accomplished and where MooTools is going over the coming weeks. It was also great to meet some of the development team in person instead of simple IRC. MooTools FTW!Read Post
dojo-namespaced objects to to allow for maximal flexibility. One of those
dojo.contentHandlers, is an object containing key->value pairs for handling the result of AJAX requests. Let me show you how to use these content handlers and how you can create your own!
Honesty hour confession: file uploading within the web browser sucks. It just does. Like the ugly SELECT element, the file input is almost unstylable and looks different on different platforms. Add to those criticism the fact that we're all used to drag and drop operations, yet up until recently, you couldn't drag files into a browser to upload them, making file uploading within the browser unintuitive. With recent advancements in browser technology, the drag and drop method is now supported, but it doesn't look good without a bit of work. Luckily MooTools Core Developer Arian Stolwijk has created a set of classes to accommodate styling drag and drop file uploading within the browser. Let's have a look at how it works!Read Post View Demo
One of the reasons I love AJAX technology so much is because it allows us to avoid unnecessary page loads. Why download the header, footer, and other static data multiple times if that specific data never changes? It's a waste of time, processing, and bandwidth. Unfortunately, at this point in the web, constant refreshes are the norm — but they don't have to be. Christoph Pojer, a MooTools Core Developer, has added History to his PojerTools PowerTools library. History replaces traditional same-site URL loading by providing a method to catch link clicks, load page content via AJAX (Mootools'
Request.HTML class), modify the document's location object to keep "history" records, and re-evaluate content links to allow developers to create a fast, efficient one-page website.