-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display more metadata #7
Comments
Maybe I'll add a panel in the upcoming "settings" page, to let the admin choose what fields to extract. And, of course, provide a default setting. Seems to be the best way to have everyone happy here :) |
Talking about metadata... I just saw you committed a patch to correct the display of aperture... but I noticed 2 things :
|
Hahaha yup it's the 50mm 1.8, so I guess you can't be wrong about that... I'm trying to fix those things, but since the EXIF is very different depending on the camera, it's quite hard. |
Yes, I understand :) |
Ah ah I think I'm going to ask you something again :D |
Yep, i only fixed the "unknown" case. The rest just doesn't work at the moment. Stay tuned, I'll definitely find a way... |
If PhotoShow allowing iptc tag (tag cloud) browsing, it will be my gallery web app. For the moment I stay with Fotoo (http://projets.kd2.org/p/fotoo-gallery/) but there is not user/group restriction.... Exemple of tag browsing : http://bohwaz.net/photos/?tags |
Good thing that it's comig up then :D But... well, I still need some time to work on it :D On 7 December 2011 09:51, VoidAndAny <
|
Great, thank you |
At least, description should be displayed under the picture in the individual picture page.
Other fields may be useful, but I'm shy of asking for them as I see that your project has an obvious focus on simplicity. But still, keywords extracted from the metadata would be nice too, for the sake of searchability.
Of course, you could extract many metadata fields and let the user configure what he wants displayed... But maybe that is not the spirit of what you are making, so I won't insist on that !
The text was updated successfully, but these errors were encountered: