Changes between Version 8 and Version 9 of QtWebKitForQt5


Ignore:
Timestamp:
Jun 6, 2011, 11:51:52 AM (14 years ago)
Author:
Simon Hausmann
Comment:

Clean ups, clear up focus on browser development

Legend:

Unmodified
Added
Removed
Modified

  • QtWebKitForQt5

    v8 v9  
    88== QtWebKit for Qt 5 ==
    99
    10 We have learned a lot about WebKit2 in the past months, as well as mobile web development. With QtWebKit for
    11 Qt 5 it is time to bring this experience to the main line:
     10We have learned a lot about WebKit2 in the past months, as well as mobile web development. It is time to bring this experience
     11to the main line of the Qt port of WebKit:
    1212
    13     * QtWebKit for Qt 5 should make it easy to write great mobile web browsers.
    14     * QtWebKit for Qt 5 provides convenient APIs for creating Qt applications that embed and closely integrate with web content.
     13    * QtWebKit for Qt 5 should be the foundation for great mobile web browsers.
    1514
    1615== Design ==
    … …  
    2019the primary graphics/UI API.
    2120
    22 Consequently the QtWebKit API should change:
     21Consequently the interface to the browser should change:
    2322
    24    * The primary interface to the web engine should be through WebKit2.
    25    * A QML based UI component offers built-in handling for gestures, touch events and scrollbars (viewport).
    26    * Features like accelerated compositing, WebGL, inline video, etc. should work out of the box, without extra settings or configuration flags.
    27    * A minimal C++ API allows for fine-tuning certain parameters and potentially low-level hooks (for example controlling the web process creation)
     23   * Our focus should be on making the WebKit2 port fast and stable enough for a browser.
     24   * A QML based UI component offers built-in handling for gestures, touch events and scrollbars.
     25   * We should not spend time designing APIs that allow for feature combinations or software fallbacks that don't make sense. Features like WebGL or video should either work out of the box properly accelerated or be disabled.
    2826   * The QWidget/QGraphicsView based WebKit1 API moves into a separate shared library that links against QtWebKit.
    2927
    3028== Implementation Details ==
    3129
    32 Let's look a bit closer into possible solutions to implement the proposed design:
     30Many different approaches to different feature have been discussed. We can record them here as a starting point for the implementation work:
    3331
    3432=== WebKit2, Scene Graph, Tiling and Accelerated Compositing ===
    35 
    36 The QML WebView should support tiling and AC out of the box. AC should not be an afterthought anymore "on top of tiling".
    37 We should be in a permanent state of accelerated composition and avoid expensive switches between AC and non-AC mode. Layers
    38 should support tiling and the root tile set should just be a layer.
    3933
    4034We need to determine the best way to integrate tiling / AC with the Qt scene graph. An initial pragmatic solution