I use django-filebrowser in a number of projects and find it invaluable. As of a while ago, Filebrowser became dependent on django- grappelli, which massively changes the default Django admin. Meanwhile, Grappelli has morphed and (I feel) become a pain in the neck to work with (buggy and difficult to configure).
There is a forked project called django-filebrowser-no-grappelli which aims to bring the good old filebrowser behavior back to the non- grappelli Django back-end, but it's not clear whether that project is stable enough for production just yet. So I feel like my editorial team is stuck with a buggy Grappelli just because they need FileBrowser, and the way out of the mess is unclear. Not an ideal situation. I've been thinking that it seems like solid file management would be a good candidate for inclusion in contrib, but wanted to put feeler out on this list to see whether others might agree. Would this make a good 1.3 feature? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
