what we usually do with the filebrowser is this: we create a custom gallery (gallery-model with gallery-images as tabularinlines) with a filebrowsefield for a folder - when you add a gallery you just select a folder on your filesystem. we overwrite the save-method (of the gallery) in order to find all images within that folder and assign the images to the gallery (via gallery-images). the thumbnails and image-versions are generated on the fly.
an example can be found here: http://www.skip.at/film/9580/bildgalerie/814/ btw: we´re working a a project coupled to the filebrowser - called "medman". using the filebrowsers signals, we store image-information (exif date) within models. medman will work with images and videos (with exif.py and ffmpeg). of couse, you can use the filebrowser signals to roll your own gallery as well ... regards, patrick On 15 Dez., 19:01, Kevin Monceaux <ke...@rawfeddogs.net> wrote: > Oops, I knew I'd leave out at least one. > > On Tue, Dec 15, 2009 at 10:42:10AM -0600, Kevin Monceaux wrote: > > Some of the items on my wish list include: > > Customizable upload/save path, preferably including a directory named > after the photo's ID, to avoid filename collisions. > > -- > > Kevinhttp://www.RawFedDogs.nethttp://www.WacoAgilityGroup.org > Bruceville, TX > > Si hoc legere scis nimium eruditionis habes. > Longum iter est per praecepta, breve et efficax per exempla!!! -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
