Changes between Version 1 and Version 2 of WebKitIDL


Ignore:
Timestamp:
Jan 27, 2012 3:15:08 PM (9 years ago)
Author:
haraken@chromium.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebKitIDL

    v1 v2  
    11= Overview =
    22
    3 The [http://www.w3.org/TR/WebIDL/ Web IDL] is a language that defines how WebCore interfaces are bound to external languages such as JavaScriptCore, V8, ObjC, GObject and CPP. We need to write IDL files to expose WebCore interfaces to those external languages. When WebKit is built, the IDL files are parsed, and the code to "bind" WebCore implementations and JavaScriptCore/V8/ObjC/GObject/CPP interfaces is automatically generated.
     3The [http://www.w3.org/TR/WebIDL/ Web IDL] is a language that defines how WebCore interfaces are bound to external languages such as JavaScriptCore, V8, ObjC, GObject and CPP. We need to write IDL files (e.g. XMLHttpRequest.idl, Element.idl, etc) to expose WebCore interfaces to those external languages. When WebKit is built, the IDL files are parsed, and the code to "bind" WebCore implementations and JavaScriptCore/V8/ObjC/GObject/CPP interfaces is automatically generated.
    44
    55This page describes practical information about how the IDL binding works and how we can write IDL files in WebKit. The syntax of IDL files are fairly well documented in the [http://www.w3.org/TR/WebIDL/ Web IDL spec], but (1) it is too formal to read:-) and (2) WebKit uses a bit different syntax due to implementation issues.
     
    99= How the IDL binding works =
    1010
    11 == JavaScriptCore ==
     11== "JavaScriptCore" ==
    1212
    13 == V8 ==
     13== "V8" ==
    1414
    15 == ObjC ==
     15== "ObjC" ==
    1616
    17 == GObject ==
     17== "GObject" ==
    1818
    19 == CPP ==
     19== "CPP" ==
    2020
    2121= IDL attributes =
    2222
    23 == [Supplemental] ==
     23== "[Supplemental]" ==
    2424
     25== "[...]" ==
    2526
     27== "[...]" ==
     28
     29== "[...]" ==
     30