You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using imagestore, and have more-or-less forked it, because I had trouble creating a custom image while I was under time pressure.
I now have a bit more time, and could pull the custom image stuff into my private repo, which would enable me to contribute the EXIF processing that I have added.
Features of my EXIF processing::
EXIF data would be exclusively for the postgres database (since it uses pgfield)
Album Upload and Image upload would parse EXIF data on images, and store in the Image() model, providing a nice accessor to get the EXIF blocks.
EXIF data is easily available in the template, via the image object.
EXIF data is cached on first use.
If you would be interested in receiving a PR with these features, and probably some other tidy-up, let me know.
If any other users are interested in having EXIF functionality, hire me for a couple of hours, and I'll get on it. Otherwise, check my fork, and help yourself.
--russ
The text was updated successfully, but these errors were encountered:
Hello,
I've been using imagestore, and have more-or-less forked it, because I had trouble creating a custom image while I was under time pressure.
I now have a bit more time, and could pull the custom image stuff into my private repo, which would enable me to contribute the EXIF processing that I have added.
Features of my EXIF processing::
If you would be interested in receiving a PR with these features, and probably some other tidy-up, let me know.
If any other users are interested in having EXIF functionality, hire me for a couple of hours, and I'll get on it. Otherwise, check my fork, and help yourself.
--russ
The text was updated successfully, but these errors were encountered: