Years ago I had a Hypercard app that took the file-list of a bunch of photos in a folder and stitched them together in a gallery. I had one index.html, a thumbs.html, and two sets of html detail documents (two for each photo), one used the 'refresh' tag and the other didn't - thereby the user could choose which set to use to 'autoplay' or not. I had a flashing red dot gif to indicate 'running' when using the auto mode.
I batch-generated the reductions and thumbnails with GraphicConverter. I could build a photo gallery for the web in about a minute. Back in 2001 javascript was to be avoided at all costs - it caused crashing and incompatibilities everywhere. A lot of text files, but it got the job done. This was used for years on the Crosby, Stills and Nash sites. ------------------------- Stephen Barncard San Francisco http://houseofcubes.com/disco.irev 2009/12/20 Sivakatirswami <[email protected]> > Stephen barncard wrote: > > Oh! that one... yes I remember when (circa 1998) I went through our old > web sites and removed all these redirects (very bad strategy from a CMS > point of view, a nightmare in fact) and I put all the redirects into a > single matrix file with a Rev cgi to drive 404's to other pages. (I still > use it today... very sweet and easy to maintain and fast) > > But I can see the utility here. No sure if there are pros or cons to using > this vs Javascript. One could add a button on the interface to post "run" to > the iRev page and then the iRev page would start inserting this into the > head... with the URL for the next slide updated on each round. If the user > clicks a "stop" button then the iRev page removes this from the head and > reverts to manual drive buttons.... > > I'll try it. Thanks! > > > > you can do the automatic advance in html using the REFRESH meta >> tag<http://en.wikipedia.org/wiki/Meta_refresh> >> >> I've built photo galleries around a lot of html pages and refresh tags. >> >> Depreciated by the W3C for redirects, but works like a champ for this >> purpose. >> >> Place inside <head> to refresh page after 5 seconds: >> >> <meta http-equiv="refresh" content="5" /> >> >> Redirect to http://example.com/ after 5 seconds: >> >> <meta http-equiv="refresh" content="5;url=http://example.com/"; /> >> >> Redirect to http://example.com/ immediately: >> <meta http-equiv="refresh" content="0;url=http://example.com/"; />. >> >> >> 2009/12/19 Sivakatirswami <[email protected]> >> >> >> >>> while waiting for the plug-in to settle down ( I can't deploy revlets >>> until >>> the update function is working) >>> >>> >>> Now, I'm wondering if there is a way to make this thing drive itself, so >>> the user does not have to click the next button, using iRev code. >>> >>> >>> >>> >> _______________________________________________ >> >> use-revolution mailing list >> [email protected] >> Please visit this url to subscribe, unsubscribe and manage your >> subscription preferences: >> http://lists.runrev.com/mailman/listinfo/use-revolution >> >> > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
