Changes between Version 16 and Version 17 of WebKit2


Ignore:
Timestamp:
Jun 15, 2016, 11:40:54 AM (9 years ago)
Author:
clopez@igalia.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WebKit2

    v16 v17  
    99== C API ==
    1010
    11 WebKit2 will provide a stable C-based non-blocking API that is mostly platform agnostic.  In order to achieve the goal of a non-blocking API, several techniques are used to make the API usable while still providing a comprehensive set of features to the embedder. These techniques include:
     11WebKit2 provides a stable C-based non-blocking API that is mostly platform agnostic.  In order to achieve the goal of a non-blocking API, several techniques are used to make the API usable while still providing a comprehensive set of features to the embedder. These techniques include:
    1212  - Notification style client callbacks (e.g. didFinishLoadForFrame)
    1313    These inform the embedder that something has happened, but do not give
    … …  
    4747== Port-Specific APIs ==
    4848
    49 We plan to build a fully non-blocking Objective-C API for Mac OS X as a wrapper on top of the C API. We believe a similar approach may be viable for other ports.
     49The Mac port provides a fully non-blocking Objective-C API as a wrapper on top of the C API.
     50The GTK+ port provides also a stable and non-blocking API: http://webkitgtk.org/reference/webkit2gtk/stable/index.html
    5051
    51 We are also not removing or obsoleting any of the existing port-specific APIs. WebCore will remain as-is, and all current APIs will continue to work and be fully supported. Thus, WebKit development and existing ports of WebKit will not be disrupted.
     52We believe a similar approach may be viable for other ports. We are also not removing or obsoleting any of the existing port-specific APIs. WebCore will remain as-is, and all current APIs will continue to work and be fully supported. Thus, WebKit development and existing ports of WebKit will not be disrupted.
    5253
    5354== Process Architecture ==
    … …  
    9697== Current Status ==
    9798
    98 WebKit2 should be considered an early technology demo. It is not yet production quality. But it's possible to try it out and see how it works at this early stage.
     99WebKit2 is production ready and stable. Different browsers are already using it like GNOME's Epiphany.
    99100
    100101== How to try it Out ==