Summary: | thumbnails needs a lot of space compared to the pictures itself | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Toralf Förster <toralf.foerster> |
Component: | Thumbs-Image | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | caulier.gilles, languitar, marian25 |
Priority: | NOR | ||
Version: | 0.9.4 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.0.0 | |
Sentry Crash Report: |
Description
Toralf Förster
2008-07-22 19:16:07 UTC
This is because digiKam follows freedesktop.org .thumbnails standard. But IMO developers should seriously consider abandoning this for several reasons: 1. PNG thumbs are too big. 2. Not interlaced images can take long time to load. 3. Standard was written several years ago and covers only files up to 256 pixels. With modern displays it is too small. Something up to 512 would be good. 4. .thumbnails directory isn't very useful on other platforms. 5. .thumbnails directory isn't portable itself. If you store your collection with database on pluggable disk and switch computers you will have to recreate thumbs on new computer. Could this have been solved by using pfg, Gilles? Ehhh, should be pgf ;) Johannes, Yes, absolutely... PGF reduce thumbnails data size against PNG. It's wavelets compression method. PGF is around at least 1/2 of PNG, and more... this depand of image content. Gilles Those thumbnails are really big compared to their parents. Sometimes the thumbnail is even bigger that the original picture. Not to mention those duplicated thumbs when you rename some folders with lots of pictures in it. There should be some function to delete those obsolete thumbnails automatically. That PGF stuff sounds good too. Marian |