-
Notifications
You must be signed in to change notification settings - Fork 239
Photologue wishlist
Here is a personal wishlist of new features; please feel free to discuss it on the mailing list and make new suggestions!
Photologue manages thumbnails internally. However, there are many 3rd party packages for creating thumbnails of images - maybe we are re-inventing the wheel, and should rip out all of this code from Photologue and instead rely on another package.
"Photologue is a huge app, and i believe if it more easy to mantain if we separate these responsibilities os management and processing. Look I'm not saying to drop this funcionality, I believe we can use them simply by calling the methods that already exist on photologue
There are a lot of packages created especifically to process images: https://github.com/SmileyChris/easy-thumbnails https://github.com/jdriscoll/django-imagekit https://github.com/globocom/thumbor"
-- Petry
Marcos Petry has started a branch to integrate ImageKit - this will be a big change, and will require a number of changes elsewhere in the project.
By this, I mean providing a way for the developer to extend these models in his project, and to tell Photologue to use these instead of the default classes.
This change will be required if we switch to ImageKit (as the developer will need a way to define custom image sizes).
As a bonus it will allow us to remove the tagging feature from Photologue - not all developers need it, so it might be better to have it as a customisation, and let Photologue concentrate on providing only core features.
Can uploading of photos be uploaded? For example, when you do an image search you can drag-and-drop an image file onto the browser window. Would such an interface improve Photologue?
If the user wants to upload many photos, they have to zip them up and upload the zip. The interface for this is clunky - we could use a JS image uploader to make the experience far more enjoyable.
A common way of displaying photos from a gallery - is it something to have as an option in Photologue?
Currently the length of this field can be set via IMAGE_FIELD_MAX_LENGTH (defaults to 100); it don't work any more because South has hard-coded a snapshot of the table definition at a point in time (as pointed out by Xavier Ordoquy). Probably this setting should be taken out, instead if the dev needs a longer field, he/she can override the field by extending the Photo model.