| |||||||||||||
The Grumpy Editor's Guide to Image Management ApplicationsThe Grumpy Editor's Guide to Image Management ApplicationsPosted Apr 19, 2005 15:02 UTC (Tue) by pizza (subscriber, #46)In reply to: The Grumpy Editor's Guide to Image Management Applications by kleptog Parent article: The Grumpy Editor's Guide to Image Management Applications
I used to use BINS, but unfortunately it doesn't scale too well. I gave up on it when it would take the better part of three hours to generate updated albums when all I did was move a few files around... But I did love the fact that it generated static HTML that needed nothing else to work.
I did submit a few patches to it over the last couple of years, but making it significantly faster would mean fundamental changes to how it works.. and the code makes my forebrain mutiny.
(Log in to post comments)
The Grumpy Editor's Guide to Image Management Applications Posted Apr 20, 2005 3:22 UTC (Wed) by kleptog (subscriber, #1183) [Link] I must agree BINS doesn't scale brilliantly, I only have a bit over 1000 images in it and it does take a little while to regenerate the images. Fortunatly it doesn't rescale/reorientate the images more than once so if you run it often enough it's not too bad.
I do think it could be made smarter, like skipping whole directories if they havn't changed but as it is it doesn't maintain enough metadata. I might patch it if it gets on my nerves... If I'm moving directories around I tend to move them in the output directory too to avoid the rescaling.
The Grumpy Editor's Guide to Image Management Applications Posted Apr 20, 2005 14:25 UTC (Wed) by pizza (subscriber, #46) [Link] Even barring keeping additional metadata, there are many, many enhancements that can be done to speed it up. Least of which is "if the jpeg file is older than the XML file, the odds are you don't need to re-parse the EXIF data." This change alone would speed things up considerably. I started to add it in, but as I mentioned before... I think I'd rather give myself a frontal lobotomy with a rusty spoon then wade that deep into the code again.
|
|||||||||||||