Changes between Version 8 and Version 9 of QtWebKitGraphics


Ignore:
Timestamp:
Nov 3, 2010 6:15:58 PM (10 years ago)
Author:
ryan.roberts@sharedresearch.jp
Comment:

fix a few formatting and type-o mistakes

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitGraphics

    v8 v9  
    33This page holds tips for web developers on how to optimize their web-code for QtWebkit's rendering pipeline.
    44The philosophy behind those performance tips is that web technologies in general are meant for dynamic '''content''' and not for dynamic '''UI'''. Therefore, most of the HTML and CSS features are optimized for exactly that. When something is slow, ask yourself: am I trying to solve a dynamic-UI problem with a tool meant for dynamic-content?
     5
    56The good news is that CSS has enough capabilities for dynamic UI, even if they're not as smooth to use as solutions originally optimized for GUI.
    67
     
    3435Be careful of high-level object-oriented nicely-designed Javascript libraries on top of the core Webkit (like Dojo or jQuery, hence the $). They make the application code look nicer, but make it hard to find the source of a performance problem, as it adds layers of complexity.
    3536
    36 If you think about what those libraries really give you, it's browser compatibility, rapid DOM element selection, and effects. If browser compatibility is what you need - those libraries are great and are definitely worth it but you might have to incur the performance compromise. rapid DOM selection can be done with document.querySelector or document.querySelectorAll, which are much faster than the browser-compatible functions. effects, if can't be expressed with CSS animations, would probably end up being slow anyway.
     37If you think about what those libraries really give you, it's browser compatibility, rapid DOM element selection, and effects. If browser compatibility is what you need - those libraries are great and are definitely worth it but you might have to incur the performance compromise. Rapid DOM selection can be done with document.querySelector or document.querySelectorAll, which are much faster than the browser-compatible functions. Effects, if can't be expressed with CSS animations, would probably end up being slow anyway.
    3738
    3839
     
    6465
    6566
    66 == Benchmarking CSS animations==
     67== Benchmarking CSS animations ==
    6768I've attached a comprehensive CSS animation test suite to this document: https://trac.webkit.org/raw-attachment/wiki/QtWebKitGraphics/cssAnimTestSuite.html
    6869Good luck!