{"id":456,"date":"2006-07-19T14:22:23","date_gmt":"2006-07-19T06:22:23","guid":{"rendered":"http:\/\/www.nargalzius.com\/blog2\/http:\/www.nargalzius.com\/blog2\/archives\/2006\/07\/2006_07_19_1422.php"},"modified":"2006-07-19T14:22:23","modified_gmt":"2006-07-19T06:22:23","slug":"instant-ajax-on-your-site","status":"publish","type":"post","link":"http:\/\/nargalzius.com\/blog\/archives\/2006\/07\/19\/instant-ajax-on-your-site","title":{"rendered":"Instant AJAX on your site"},"content":{"rendered":"

I went back to the music section<\/a>, and redid the AJAX<\/code> code I used. I remembered the Prototype library<\/a> (prototype.js<\/code>) I was using for the lightbox had its own AJAX<\/code> object class – which was much more comprehensive than my implementation (error handling, browser support, etc).<\/p>\n

I thought that since I was already<\/em> using the framework anyways, might as well redo my functions altogether to utilize<\/em> it. While the documentation<\/a> had example codes, like any other site, I noticed that usually they always include a fixed “target” in the function. Meaning if you have a certain AJAX<\/code> operation you wish to perform, the function usually took in the URL<\/code> which you specify, but plugs it into a set<\/strong> target. While this is easily fixed, I was simply baffled as to why they don’t make it a standard to “assume” people would want at least to specify both the url<\/code> and<\/strong> target<\/em> as a default.<\/p>\n

So I came up with code which I dubbed “InstA-JAX”<\/em> to do just that. I’m sharing it here since I figured that anyone I know who is remotely interested in implementing rudimentary AJAX functionality might find it very useful as it doesn’t require them to “think” anymore hehehehe. – just plug it in, markup your HTML the proper way and you should be good to go.<\/p>\n\n

Here’s the code. Just drop it somewhere between your <head><\/code> tags – or import it via .js<\/code> file if that’s your thing.<\/p>\n