OK. Got some more fleshed out:
http://www.thinkdreams.com/devzen/index.php?album=njsummer&image=IMG_2120.JPG
If you note, it displays the image information before the print_r statement (which prints out all the raw data). Thus I have most of the common EXIF information now stored as variables, which you should be able to take a then cache in the DB using the functions you're writing. Once we have the data in the DB, then we can do fancier stuff like automatic image rotates if it's out of rotation, etc.
I've sent this to you via email Tristan. See what you can make of it, and let me know how you want me to proceed further. I think I've covered most of the major variables. A lot of the maker data for specific camera models is pretty much redundant or unnecessary IMHO.
Tristan's looking at the code right now, but here's what changes I've made so far:
Modified Exifixer libs and added function to assign exif tags to variables.
Modified image.php to add display of raw EXIF data and variable data.
If you send your email address to me at craig@thinkdreams.com I'll be happy to send the changed files to you. I'm using the effervescence theme for testing, but you should be able to drop the code into any theme.
And as far as docs Stef, Tristan's started fleshing out the documentation on the wiki, and I think that's where the docs will live. I would imagine we'd eventually see a PDF version or whatever, but the wiki format is fine by me because it's always available.
The docs are very much in the beginning stages, so don't expect a large amount of user information until more contributions are made to it. Feel free to contribute though!
Sorry Stef- Hang on. Got your email. Tris is right. Never enough time. Especially when they change daylight savings time on us.....
@thinkdreams
Thanks for your code. It works. I thinking about how to put this information inside MySQL or should we
wait for Tristan?
What about your theme "thinkdream"? Does it make sense to upgrade them to exifer?
@trisweb, thinkdreams
Is there a way with svn to merge the different code variants together? Do we have different code
branches?
I think we should continue to submit as patches rather than creating a new branch for it. Might get confusing after a while, considering you're also looking at RSS (hopefully) soon too for 1.1.
And take your time. Have to pay the bills somehow. I might be in and out the next two weeks anyway, as it's Linux training time for my company...