I’m trying to figure out a way that I can display an image via target show/hide action when clicking on a thumbnail where the large image shows with an image caption below the image and an image ID (some alphanumericals) to the top left for image identification.
How would I set that up? Would I store the image’s caption and ID in and retrieve it from the image’s IPTC data? I’m clueless…
If you use Target show/hide layer then your layer can consist of an HTML box that within has a graphic box for your picture and an HTML box below for your caption.
Thanks. But how would I best store and reference the image’s caption and ID number? If I have to keep manual lists of hundreds of pictures (leaving aside the time for setup) that would be horrible and a source of error. Is there a better idea? That’s why I was wondering if there is a possibility to put these two pieces of information in the IPTC data of the picture and extract that from within Freeway somehow…
Wow, sounds like a job for a dedicated image manager of one sort or another.
Actions don’t have access to IPTC data, but server-side or desktop applications do. You might want to look on Hotscripts for a PHP-based image library app, like Coppermine. That will have all sorts of tagging and metadata read support that you couldn’t get from Freeway under any circumstances.
Another approach would be to use a desktop app like Aperture, Lightroom, iPhoto, or Expression Media (formerly iView MediaPro) to organize your pictures and to automate the export of HTML galleries. You’ll be able to integrate those with Freeway to a limited extent through iframes or traditional framesets.
Thanks, Dave and Walter. I had feared that it isn’t possible so easily. The main idea is to show photography on a website with a caption under the picture and some identifier so that someone interested in a fine art print can use that identifier to unambiguously order a (correct) print. I don’t want to use any of the applications you mentioned, Walter, as they don’t come anywhere near what I believe is good looking. As a matter of fact I like Carousel better.
I’m looking at probably 50 pictures to start with and then growing to a couple of hundred.
Presumably split over several pages/galleries.
This is a manageable amount if you keep the amount of images per page down as too big a carousel or too many images on a page will make a slow/heavy page.
Why not use the FW shop actions - the buy buttons could be included in a carousel or a target layer.
