-
Notifications
You must be signed in to change notification settings - Fork 237
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
Extendable Gallery and Photo models #49
Comments
Note: will need documentation to explain how it works + some unit tests. |
The new User model in Django 1.5 could be a good design to follow. |
Note: @xordoquy indicated at the last DjangoCon that he would be very interested in this feature and might code it - anyone interested in working on this should contact him first to avoid any duplicated effort! |
Started some work on my way back to Paris.
See https://github.com/linovia/django-photologue/tree/feature/customizable_models |
Woah, that was fast. I need to catch up with work for various clients over the next few days, but next weekend is 'jour férié' here in the UK so I will certainly look at it then! |
Actually it's still work in progress. Still need to make sure ti works with a custom model. |
Tried my hand at extending the Gallery model - @xordoquy, I didn't want to interfere with your work on extending Photos, and I wanted to understand a bit better myself how this feature works. I've put my work so far on branch 'dynamic_models'. |
Hi @richardbarran, indeed it's for Django 1.5 |
As per title.
If we can make these models extendable by the user, we will make them a lot more useful - in particular it will help with django-imagekit so that users can create custom effects etc... for their project.
Could be based on something similar to what is used for Django-oscar, so Gallery and Photo could be abstract classes; the user can import and extend these models in his own project, and use settings to tell Photologue about these new models.
Whenever Photologue import Gallery or Photo, it will search first for a model defined in the settings, then fall back to its own version.
The text was updated successfully, but these errors were encountered: