Following up on bug 24524, do the same for InspectorResource. This change is somewhat more involved. In addition to straight refactoring of JS calls, I made tracking resource changes data-driven (bit vector), rather than logic-driven, and moved it into the InspectorResource itself. The advantage is that now InspectorController can now just call InspectorResource::updateScriptResource and it will figure out which bits have been changed.
Created attachment 29172 [details] refactor InspectorResource to use ScriptObject/FunctionCall, v1. WebCore/ChangeLog | 76 ++++ .../bindings/js/JSInspectorControllerCustom.cpp | 14 +- WebCore/bindings/js/ScriptFunctionCall.cpp | 6 + WebCore/bindings/js/ScriptFunctionCall.h | 1 + WebCore/bindings/js/ScriptObject.cpp | 71 ++++ WebCore/bindings/js/ScriptObject.h | 10 + WebCore/inspector/InspectorController.cpp | 434 +++----------------- WebCore/inspector/InspectorController.h | 16 +- WebCore/inspector/InspectorController.idl | 4 +- WebCore/inspector/InspectorResource.cpp | 315 +++++++++++--- WebCore/inspector/InspectorResource.h | 121 ++++-- 11 files changed, 571 insertions(+), 497 deletions(-)
Landed as http://trac.webkit.org/changeset/42155.