a jQuery slideshow plugin
The package is based around the way you already build your website, so you don’t have to retain swaths of arbitrary knowledge to use it on a regular basis.
At 15kB for the full version, and a minute 6kB for the hyper-compressed version, and tidy code, this plugin won’t bog down your site
or burn out your users’ browsers, even using it in multiple iterations per page.
With the little markup you need to add to your site, you get a full featureset, like the ability to put whatever data you want within the slide window, even mixed types, a proportionally-correct status display that configures itself, fullscreen display and swipe functionality.
Add some slick usability
to your site with a plugin that’s fun and easy to use. And if you have any other questions, I’ll be happy
to help you out.
In IE: Invalid argument/Object doesn't support this property or method Corrected as of 11:16 p.m. 11/7/2010
This odd bug sprang up recently, and essentially involves Internet Explorer throwing a hissy fit over the simpleSlide-tray element not having a zeroed out margin. It was fairly tough to track down, as it was completely style related. The script will now handle this, so it will work whether you have a CSS reset or not.
Images slideshows won't work in Firefox Corrected as of 12:12 p.m. 11/7/2010
I recently released a version of the script that contained some debug code by way of console.log() commands. For some reason as yet unbeknownst to me, these lines were obstructing the script's ability to complete unless Firefox had Firebug up and running. All I can figure is that it doesn't like console.log commands if theres no console to send it to (other browsers have a resident console). At any rate, just update to the latest version of the script, and you'll be fine. Sorry for the confusion.
I can't get the multiple iterations to work correctly... Answer courtesy of James Billot, 9:52 a.m. 11/30/2010
There have been reports of the plugin not handling multiple iterations of sliders well, wherein later sliders on the page wouldn't appear. What's actually happening is that the sliders are there and initialized, but since SimpleSlide doesn't always have a height or width measurement to go from, the plugin can't give the outer slide window its own dimensions. You can remedy this by giving the first image in each slider an explicit inline "height" and "width" attribute, e.g. <img src="image.jpg" height="100" width="100"/>. I've also updated the code a bit to handle loading images a bit more cleanly. It's not a fool-proof process, but it should be able to do the trick at this point. Please let me know if you are still facing issues with this annoying bug.
Fullscreen Bug Corrected as of 5:57 p.m. PST, 5/11/2010
The fullscreen functionality was not acting consistently correctly, especially when resizing from vertically-oriented to horizontally or vice versa. The issue has been corrected. Also note that the sample code at the bottom of the "more uses" section regarding implementation of the fullscreen capabilities has been updated for usability and stability.
The First-Time Plugin Writer's Bug Corrected as of 11:46 p.m. MST, 4/16/2010
The namespace for simpleSlide was incorrectly established, and as a result, some may have had some trouble using the plugin in conjunction with other plugins/frameworks/etc. This issue has been fixed and simpleSlide now lives in its own namespace. Thank you to the individual who pointed this issue out while in the process of trying to make SS work with his Wordpress configuration, you know who you are ;) . Also fixed was an issue with simpleSlide disliking its plain vanilla (no-parameter) call
simpleSlide();, and thusly returning an error.
Status Bar Bug Corrected as of 11:44 a.m. MST, 4/12/2010
This bug sprang up after some recent code optimization that had been performed to shrink down the size of the file a bit more. If your status bar is behaving erratically, please redownload the script, as I've replaced the files with updated and (hopefully) working counterparts. When all's said and done, you should only need to replace the file that you're using. Thanks to all who pointed out this issue.
Please follow this link to contact me about any more issues you have met with. Thanks again.