On 14.Jan 2005 - 13:43:32, Philip Dicke wrote:
> >It's going to be something I need myself for now - preparing my
> >digital photos for website photoalbum
> For my digital photos I use digikam :-)
> Although I don't know if it has a way to add comments
It has comments support...
> or publishing output plugins, which would be a fantastic idea if it
> doesn't already have those options.
Export is empty here, as is "batch processing".
> I do know it has themes, the ability to rotate, and remove red-eye
I did not see red-eye reduction
> You might want to invest some time looking at it so see
> if with some modification it could suite your needs before writing
> something from scratch. No need to re-invent the wheel here.
Actually: yes there is, because I'm planning a much larger application
(kind of kmusicdb, but that one doesn't fit my needs, nor das prokyon
or anything else I tested) and I take this as an excercise. Also I
don't quite find digikam's UI proper for my needs, it's too large, has
too much stuff in it. My app is not necessarily just for photos and
for now there's now support for digital cameras at all (I fetch the
pics via card reader because it's much faster). Last but not least:
Diversity is never bad (IMHO).
> So for your case, you'll generally be looking at thumbnails and
> viewing/editing 1 photo at a time. I would pre-generate all the thumbnails
> when you load a directory (some applications in KDE store the thumbnails on
> the hard drive as a cache)
That would happen anyway, as I'm going to use a KIconView...
> and for the rest of the images I suggest working
> with one at a time, only loading 1 image. For that image I would keep both
> the QPixmap and the QImage in memory. See how that works. > If changing
> images takes too long, then you can attempt to predict which image you will
> work with next and load it in the background.
Prediction might be pretty easy, as I'm probably going from one to
next image (maybe leaving out a couple...)
> Anyway I would do some sort of profiling to see what takes the longest,
> reading the image from disk or the conversion to a pixmap. Also how much
> memory QImage and QPixmap uses could determine how many images you want to
> keep in memory.
Thats probably best thing to do, thanks for the hints.
While you recently had your problems on the run, they've regrouped and
are making another attack.
List archive and information: http://lists.trolltech.com/qt-interest/