What do you think about adding support for django-filebrowser as some kind of "custom backend", instead of using easy-thumbnais.
The FileBrowser is an extension to the Django administration interface in order to:
browse directories on your server and upload/delete/edit/rename files.
include images/documents to your models/database using the FileBrowseField.
select images/documents with TinyMCE.
It already has a feature that allows you to generate thumbnails from images, but the versions are hard-coded into settings.
There's no support for crop definitions generated by users, like ImageRatioField.
I think that with little work, we can put these 2 great projects to work together.
I've an open issue at django-filebrowser querying some guidance on how to accomplish this. I think that at least It will need some kind of pipeline, as easy-thumbnails does.
With some hacks, I got the ImageRatioField working with a FileBrowseField (instead of ImageField), but still using easy-thumbnails to generate thumbnails. I want to get full integration, as an option to completely replace easy-thumbnails.
Hi!
What do you think about adding support for django-filebrowser as some kind of "custom backend", instead of using
easy-thumbnais.The FileBrowser is an extension to the Django administration interface in order to:
It already has a feature that allows you to generate thumbnails from images, but the versions are hard-coded into settings.
There's no support for crop definitions generated by users, like
ImageRatioField.I think that with little work, we can put these 2 great projects to work together.
I've an open issue at django-filebrowser querying some guidance on how to accomplish this. I think that at least It will need some kind of pipeline, as
easy-thumbnailsdoes.With some hacks, I got the
ImageRatioFieldworking with aFileBrowseField(instead of ImageField), but still usingeasy-thumbnailsto generate thumbnails. I want to get full integration, as an option to completely replaceeasy-thumbnails.What do you think?