-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ævar Arnfjörð Bjarmason schrieb:
It's be nice if it could collapseable like the TOC, and be collapsed by default. It'd also be nice to gather some stats on the camera models used, if some are more likely to produce featured pictures, etc.
It would be nice if the look didn't suck in general.
When Magnus initially added the support he made the table appear before the image and aligned it to the right, this had the negative side-effect of having a huge table before the image (as opposed to floating beside the image) when the image was too big to fit the table beside it, so I moved it. It would be nice if we could have the middle ground of beside the image if it fits and below it (not above) if it doesn't.
We could always limit the table width, and then make the user set the maximum image preview width in his preferences manually :-]
Regarding statistics that wouldn't be practically possible (fast) unless we added a new table named image_metadata and had a seperate field for each valid EXIF tag (of which there are alot), then we could add an advanced Image search.
IMHO the chances for someone desperately needing to search for all images taken with a specific camera model or similar are pretty slim. The vast majority of people will search for names (places, people), types/context (beach, church, person) etc.
For doing some statistics, a dozen new fields or so might be overkill. A statics-gathering task could run once a week or so, reading each and every entry and doing statistics internally, then sum them up on a single page.
If, for some reason, there's pressing need for fast searching of EXIF data, maybe a new table (exif_image_id,exif_key,exif_value) would be in order; that way, we can store all keys flexible (as a string), without having to create a new field for every single key (and update and maintain these, if the standard changes).
Magnus