{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"open","user":{"avatar_url":"https://secure.gravatar.com/avatar/667bd007bac994a1441386ac4d2beb2b?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"667bd007bac994a1441386ac4d2beb2b","url":"https://api.github.com/users/hcarvalhoalves","login":"hcarvalhoalves","id":161577},"milestone":null,"assignee":null,"labels":[],"updated_at":"2011-11-11T18:42:25Z","comments":1,"closed_at":null,"url":"https://api.github.com/repos/sehmaschine/django-filebrowser/issues/45","body":"The versions feature is very useful, but some sites (specially high-traffic) will adopt other strategies for generating thumbnails, rendering filebrowser less useful than it could be. Some sites also have to deal with legacy media, and that doesn't play well with filebrowser's notion of \"versions\".\r\n\r\nIt would be interesting to decouple the versions functionality from the core to allow it's usage for managing files *only*. This could be easily accomplished by providing simpler `FileObject` and `FileBrowserSite` classes that are unaware of versions, and then providing a `filebrowser.versions` app that augments on that and provides the versioning methods, management commands and additional templates.\r\n\r\nI made a fork without the versions features (since I didn't needed), and removing the unwanted code was very simple (the code is well decoupled already). If there's interest it can be used as a base for refactoring:\r\n\r\nhttps://github.com/hcarvalhoalves/django-filebrowser\r\n\r\nSorry for opening a ticket without a patch, this is more of a suggestion. Since I won't use the versions functionality I don't have the time right now to make up a patch, but I wanted to move the idea forward.","html_url":"https://github.com/sehmaschine/django-filebrowser/issues/45","title":"Versions feature could be refactored into an optional app","number":45,"id":2202421,"created_at":"2011-11-10T20:36:25Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/afebfc47e8dfbecb51319218ec29bc41?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"afebfc47e8dfbecb51319218ec29bc41","url":"https://api.github.com/users/sehmaschine","login":"sehmaschine","id":185432},"updated_at":"2011-11-11T18:42:25Z","url":"https://api.github.com/repos/sehmaschine/django-filebrowser/issues/comments/2711603","body":"some thoughts & questions:\r\n\r\n1. versions are not about thumbnails.\r\n2. what´s the problem with legacy media?\r\n3. what exactly are the benefits if we decouple the versions-app? because if you don´t need versions, it´s not in your way, right?\r\n4. how do you deal with images on a grid-based website if you don´t use versions?\r\n\r\nthanks,\r\npatrick","id":2711603,"created_at":"2011-11-11T18:42:25Z"}}