Changes between Version 16 and Version 17 of ProposedWebInspectorRearchitecting


Ignore:
Timestamp:
Sep 19, 2008 1:02:25 PM (14 years ago)
Author:
Dimitri Glazkov
Comment:

started on message format

Legend:

Unmodified
Added
Removed
Modified
  • ProposedWebInspectorRearchitecting

    v16 v17  
    113113Completely decoupling `InspectorController.cpp` from the JS side will require converting the creation of JS objects on C++ side from property->object->constructor-based approach to more JSON-ey approach, where the objects don't have a specific prototype chain and look more like IPC messages. This in turn will require some refactoring of inspector's JS code to either create prototype-based objects at receiving point or adapt to using new style of messages. ''Perhaps that would make the inspector code a bit more slender and more JavaScript-ey anyway?''
    114114
     115== Message Format ==
     116
     117Event (Notification Message):
     118
     119{{{
     120<event> ::= {
     121  "type"    : "event"
     122  "target"  : "console" | "database" | "resource" | ...
     123  "event"   : "new-message" | ...
     124  "body"    : <body>
     125}
     126}}}
     127
     128=== console/new-message Body Format ===
     129
     130{{{
     131<body> ::= {
     132  "source"      : "html" | "xml" | "js" | "css" | "other",
     133  "level"       : "tip" | "log" | "warning" | "error" | "object" | "node" | "startGroup" | "endGroup",
     134  "line"        : <number>,
     135  "url"         : <string>,
     136  "groupLevel"  : <number>,
     137  "args"        : [
     138    <message-argument>, ...
     139  ]
     140}
     141
     142<message-argument> ::= <node> | <string>
     143
     144<node> ::= {
     145  ...
     146}
     147
     148}}}
     149
     150
    115151== BUGS FILED ==
    116152