Changes between Version 12 and Version 13 of ProposedWebInspectorRearchitecting


Ignore:
Timestamp:
Sep 17, 2008 2:43:26 PM (14 years ago)
Author:
Dimitri Glazkov
Comment:

added random notes

Legend:

Unmodified
Added
Removed
Modified
  • ProposedWebInspectorRearchitecting

    v12 v13  
    106106For making sure the inspector has zero impact on page load times and minimal impact on memory usage we agreed on a few UI changes. Network monitoring and possibly debugging should be opt-in per-site. The console should only keep around XXX messages unless the user opts-in to keep more (all?) messages for that site. Currently, Chromium has XXX==100, but that was a relatively arbitrary decision. As a side note, the Chromium/V8 debugger is already zero cost until a debug statement is actually hit, so Chromium doesn't actually care about the debugger being opt-in.
    107107
     108== Other random work-in-progress notes ==
     109
     110Completely decoupling `InspectorController.cpp` from the JS side will require converting creation of JS object 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 cleaner and more JavaScript-ey anyway?''
     111
    108112== BUGS FILED ==
    109113