Changes between Version 15 and Version 16 of ProposedWebInspectorRearchitecting

Timestamp:

Sep 18, 2008, 9:00:59 AM (16 years ago)

Author:

Dimitri Glazkov

Comment:

WebKit -> WebCore rename

ProposedWebInspectorRearchitecting

@@ -21 +21 @@
 == What's There Now ==
 
-Currently, communication between Inspector and !WebKit occurs via two JS objects:
+Currently, communication between Inspector and !WebCore occurs via two JS objects:
 
- * `InspectorController`, created by !WebKit and populated with methods that JS invokes to talk to WebKit.
- * `WebInspector`, created on the JS side and used by !WebKit to talk back to inspector. Only a small fraction of `WebInspector`'s methods is actually used for this.
+ * `InspectorController`, created by !WebCore and populated with methods that JS invokes to talk to WebKit.
+ * `WebInspector`, created on the JS side and used by !WebCore to talk back to inspector. Only a small fraction of `WebInspector`'s methods is actually used for this.
 
-For instance, when the messages in the console are cleared by the user, the `InspectorController.clearMessages()` is invoked to reset the corresponding `m_consoleMessages` in !WebKit. Conversely, whenever !WebKit has a new message to display on the console, it creates a `ConsoleMessage` JS object and then invokes `WebInspector.addMessageToConsole()` with that object as an argument. It is up to Inspector's JS code to initialize `WebInspector` object and its methods.
+For instance, when the messages in the console are cleared by the user, the `InspectorController.clearMessages()` is invoked to reset the corresponding `m_consoleMessages` in !WebCore. Conversely, whenever !WebCore has a new message to display on the console, it creates a `ConsoleMessage` JS object and then invokes `WebInspector.addMessageToConsole()` with that object as an argument. 
+
+It is up to Inspector's JS code to initialize `WebInspector` object and its methods.
+
 
 = APIs to implement =