Changes between Version 15 and Version 16 of QtWebKit/CodeCamp200912


Ignore:
Timestamp:
Dec 16, 2009 5:57:35 AM (10 years ago)
Author:
zecke@selfish.org
Comment:

link to the presentation to freya and mozAfterPaint

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKit/CodeCamp200912

    v15 v16  
    2020 * Antti is talking about tile based rendering. A working prototype is using QImage to paint in a thread. To make it general usable and accelerate Qt needs to gain the ability to draw to a QPixmap from different threads. One of the limitations will be handling certain CSS attributes that will be ignored just like the iPhone, WebOS and such. It was discussed if tiling should be supported for QWebView and QWebGraphicsView or only for the QWebGraphicsView. We have not drawn a conclusion.
    2121
    22  * Presentation on how to support JavaScript programmers to see what is going on. Currently a JavaScript API to expose information about painting is exposed. This API is similiar to the Mozilla mozAfterPaint Event. This way a JavaScript developer can see which content will be redrawn due his code. Another thing is to export the FPS count for drawing to the JavaScript developer. This somehow relates to the WebTime effort of the W3C. In the future we will need a heap profiler that will show the heap usage for each callframe of the JavaScript execution and finally we need the ability to do this on the device and get the data on the host.
     22 * [https://trac.webkit.org/attachment/wiki/QtWebKit/CodeCamp200912/Performance%20JS%20APIs.pdf Presentation] on how to support JavaScript programmers to see what is going on. Currently a JavaScript API to expose information about painting is exposed. This API is similiar to the Mozilla mozAfterPaint Event. This way a JavaScript developer can see which content will be redrawn due his code. Another thing is to export the FPS count for drawing to the JavaScript developer. This somehow relates to the WebTime effort of the W3C. In the future we will need a heap profiler that will show the heap usage for each callframe of the JavaScript execution and finally we need the ability to do this on the device and get the data on the host.
    2323
    2424 * BenjaminP was talking about plans for Qt4.7 to regularily run benchmarks during the development cycle and to  automate and store these results.
     
    2727
    2828
    29  * Zoltan was talking about a new valgrind skin called [http://webkit.sed.hu/node/29 freya] to instrument memory usage including showing how much and who was allocating the memory. The special thing about freya is that it has a powerful configuration file that allows to combine various call frames, or omit certain things that are not interesting. The biggest limitation for him is that freya and the JavaScript JIT refuse to cooperate.
     29 * Zoltan was talking about a new valgrind skin called [http://webkit.sed.hu/node/29 freya] ([https://trac.webkit.org/attachment/wiki/QtWebKit/CodeCamp200912/WkMem.pdf presentation]) to instrument memory usage including showing how much and who was allocating the memory. The special thing about freya is that it has a powerful configuration file that allows to combine various call frames, or omit certain things that are not interesting. The biggest limitation for him is that freya and the JavaScript JIT refuse to cooperate.
    3030
    31312nd Day