Changes between Version 11 and Version 12 of QtBackLog

Timestamp:

Oct 18, 2009, 7:50:04 AM (15 years ago)

Author:

zecke@selfish.org

Comment:

--

QtBackLog

@@ -16 +16 @@
  * QBENCHMARK results are hard to analyze and compare. We need a single and simple way to say if something is faster or slower. Be a bit like sunpsider, do the same math as well, mention slowest and fastest run.
 
- * Make picking a QImageIOHandler in QImageReader faster
+ * Make picking a QImageIOHandler in QImageReader faster. Currently even the TIFF plugin is asked to handle images.
 
  * Bring zero-copy to QIODevice... big one. That is good for networking and image decoding.
 
- * Cut down on usage of QImage::scanLine inside Qt.
+ * Cut down on usage of QImage::scanLine inside Qt. This was already done in the GIF and PNG decoder. Patch is to be merged.
 
- * Make QGifHandler::imageCount scan through the images.
+ * Make QGifHandler::imageCount scan through the images. This can give a 5% speedup in the image_cycling reduction.
 
 === QtWebKit problems ===
@@ -39 +39 @@
  * Go through the Palm changes and consider adopting them. Currently candidates are: Use stack/class memory in CSSParser, use JDCT_Fast for Jpeg decoding (to be achieved with QImageReader to set quality to 49), changes to Cached* to throw away encoded data more early. Palm avoids floating point operation on premultiplied alpha in setRGBA.
 
- * Using QImageReader::setQuality(49) shows a 20msec (from 440msec to 420msec) improvement in the image_cycling test case reduction. 
+ * Using QImageReader::setQuality(49) will use JDCT_IFAST and promises to give a 5% speedup on image_cycling.