Changes between Version 32 and Version 33 of WebKitIDL

Timestamp:

Feb 15, 2012, 10:34:00 PM (14 years ago)

Author:

haraken@chromium.org

Comment:

--

WebKitIDL

@@ -678 +678 @@
 === * [CustomConstructor](i), [JSCustomConstructor](i), [V8CustomConstructor](i), [ConstructorParameters](i) ===
 
-Summary: They allow to write custom bindings for constructors.
+Summary: They allow us to write custom bindings for constructors.
 
 Usage: They can specified on interfaces.
@@ -698 +698 @@
  * [JSCustomConstructor] on an interface indicates that you want to write JavaScriptCore custom bindings for the constructor.
  * [V8CustomConstructor] on an interface indicates that you want to write V8 custom bindings for the constructor.
- * [CustomConstructor] is equivalent to [JSCustomConstructor] and [V8CustomConstructor].
+ * [CustomConstructor] is equivalent to [JSCustomConstructor, V8CustomConstructor].
 
 For example, if you specify [Constructor, JSCustomConstructor],
@@ -809 +809 @@
 === * [CustomToJSObject](i), [JSCustomToJSObject](i), [V8CustomToJSObject](i) ===
 
-Summary: It allows us to write custom 
-
-Usage: 
+Summary: They allow us to write custom toJS() or toV8().
+
+Usage: They can be specified on interfaces:
+{{{
+    interface [
+        CustomToJSObject
+    ] XXX {
+    }
+}}}
+
+ * [JSCustomToJSObject] on an interface indicates that you want to write custom toJS().
+ * [V8CustomToJSObject] on an interface indicates that you want to write custom toV8().
+ * [CustomToJSObject] is equivalent to [JSCustomToJSObject, V8CustomToJSObject].
+
+By default, toJS() and toV8() are automatically generated in JSXXX.h and JSXXX.cpp or V8XXX.h and V8XXX.cpp.
+With [CustomToJSObject]/[JSCustomToJSObject]/[V8CustomToJSObject],
+you can write custom toJS() or toV8() in WebCore/bindings/js/JSXXXCustom.cpp or WebCore/bindings/v8/custom/V8XXXCustom.cpp.
 
 === * [CheckDomainSecurity](i), [DoNotCheckDomainSecurity](m,a), [DoNotCheckDomainSecurityOnGetter](a), [DoNotCheckDomainSecurityOnSetter](a) ===
@@ -843 +857 @@
 === * [CustomCall](i) ===
 
-=== * [JSCustomToNativeObject](i), [JSCustomFinalize](i), [JSCustomIsReachable](i), [JSCustomMarkFunction](i), [JSCustomNamedGetterOnPrototype](i), [JSCustomPushEventHandlerScope](i), [JSCustomDefineOwnProperty](i), [JSCustomGetOwnPropertySlotAndDescriptor](i), [JSCustomDefineOwnPropertyOnPrototype](i) ===
+=== * [JSCustomToNativeObject](i), [JSCustomFinalize](i), [JSCustomIsReachable](i), [JSCustomMarkFunction](i), [JSCustomNamedGetterOnPrototype](i), [JSCustomPushEventHandlerScope](i), [JSCustomDefineOwnProperty](i), [JSCustomDefineOwnPropertyOnPrototype](i), [JSCustomGetOwnPropertySlotAndDescriptor](i) ===
+
+Summary: They allow us to write custom code for the JavaScriptCore code which would be generated automatically by default.
+
+Usage: They can be specified on interfaces:
+{{{
+    interface [
+        JSCustomToNativeObject,
+        JSCustomFinalize,
+        JSCustomIsReachable,
+        JSCustomMarkFunction,
+        JSCustomNamedGetterOnPrototype,
+        JSCustomPushEventHandlerScope,
+        JSCustomDefineOwnProperty,
+        JSCustomDefineOwnPropertyOnPrototype,
+        JSCustomGetOwnPropertySlotAndDescriptor
+    ] XXX {
+    }
+}}}
+
+You can write the following custom code in WebCore/bindings/js/JSXXXCustom.cpp.
+Refer to use cases in WebCore/bindings/js/JSXXXCustom.cpp for more details.
+
+ * With [JSCustomToNativeObject], you can write custom toXXX(...):
+{{{
+    PassRefPtr<XXX> toXXX(JSGlobalData& globalData, JSValue value)
+    {
+        ...;
+    }
+}}}
+ * With [JSCustomFinalize], you can write custom JSXXXOwner::finalize(...):
+{{{
+    void JSXXXOwner::finalize(JSC::Handle<JSC::Unknown> handle, void* context)
+    {
+        ...;
+    }
+}}}
+* With [JSCustomIsReachable], you can write custom JSXXXOwner::isReachableFromOpaqueRoots(...):
+{{{
+    bool JSXXXOwner::isReachableFromOpaqueRoots(JSC::Handle<JSC::Unknown> handle, void* context, SlotVisitor& visitor)
+    {
+        ...;
+    }
+}}}
+ * With [JSCustomMarkFunction], you can write custom JSXXX::visitChildren(...):
+{{{
+    void JSXXX::visitChildren(JSCell* cell, SlotVisitor& visitor)
+    {
+        ...;
+    }
+}}}
+ * With [JSCustomNamedGetterOnPrototype], you can write custom JSXXX::putDelegate(...):
+{{{
+    bool JSXXX::putDelegate(ExecState* exec, const Identifier& propertyName, JSValue value, PutPropertySlot& slot)
+    {
+        ...;
+    }
+}}}
+ * With [JSCustomPushEventHandlerScope], you can write custom JSXXX::pushEventHandlerScope(...):
+{{{
+    ScopeChainNode* JSXXX::pushEventHandlerScope(ExecState* exec, ScopeChainNode* node) const
+    {
+        ...;
+    }
+}}}
+ * With [JSCustomDefineOwnProperty], you can write custom JSXXX::defineOwnProperty(...):
+{{{
+    bool JSXXX::defineOwnProperty(JSObject* object, ExecState* exec, const Identifier& propertyName, PropertyDescriptor& descriptor, bool throwException)
+    {
+        ...;
+    }
+}}}
+ * With [JSCustomDefineOwnPropertyOnPrototype], you can write custom JSXXXPrototype::defineOwnProperty(...):
+{{{
+    bool JSXXXPrototype::defineOwnProperty(JSObject* object, ExecState* exec, const Identifier& propertyName, PropertyDescriptor& descriptor, bool throwException)
+    {
+        ...;
+    }
+}}}
+ * With [JSCustomGetOwnPropertySlotAndDescriptor], you can write custom JSXXX::getOwnPropertySlotDelegate(...) and JSXXX::getOwnPropertyDescriptorDelegate(...):
+{{{
+    bool JSXXX::getOwnPropertySlotDelegate(ExecState* exec, const Identifier& propertyName, PropertySlot& slot)
+    {
+        ...;
+    }
+
+    bool JSXXX::getOwnPropertyDescriptorDelegate(ExecState* exec, const Identifier& propertyName, PropertyDescriptor& descriptor)
+    {
+        ...;
+    }
+}}}
 
 === * [JSCustomHeader](i) ===