Finishing a Slide Show Application with jQuery - Listing the application’s complete source code (Page 4 of 4 )
(definition of 'slide_show.htm' file)
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Thanks to the functionality of the jQuery library, building a simple slide show like the one shown above only requires a couple of source files. In this specific case, the first of these files, called “slide_show.htm,” is responsible for retrieving a bunch of images from the web server via Ajax, while the second one, named “getimage.php,” is charged simply with sending the HTML code of the images in question to the client. Not too hard to understand, right?
If you’re interested in trying out this Ajax-based application with your own machine, you may want to use the following sample images for testing purposes. Here they are:
Now that you have at your disposal the three images shown above, feel free to use them if you wish to test this Ajax-based slide show using your own web server. And finally, don’t forget to download jQuery’s source file from its official web site, at: http://jquery.com. It’s going to be a fun and educational experience, trust me!
Sad but true, we’ve come to the end of this series. The journey has been pretty instructive, since you learned how to use the handy “$.ajax()” method bundled with the jQuery to develop a simple Ajax-driven slide show.
As you saw earlier, the logic that drives this particular web application is actually simple to follow, and should give you a clear idea of how to use the Ajax module of jQuery in all sorts of clever ways.
See you in the next web development tutorial!
DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.