summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authoryurys@google.com <yurys@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2009-02-20 11:14:55 +0000
committeryurys@google.com <yurys@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2009-02-20 11:14:55 +0000
commit5e1ce07a5f99e59bfe961c70e1d5cc2bf8f4fd86 (patch)
treec311ca8cfad3579e526aa6e8f97b6aff0b68ccdc /tools
parenta10c64530127a1e735b8e7a0d4eb8351e3ef65d2 (diff)
downloadchromium_src-5e1ce07a5f99e59bfe961c70e1d5cc2bf8f4fd86.zip
chromium_src-5e1ce07a5f99e59bfe961c70e1d5cc2bf8f4fd86.tar.gz
chromium_src-5e1ce07a5f99e59bfe961c70e1d5cc2bf8f4fd86.tar.bz2
Add tab content type for developer tools UI.
Add code routing messages between ToolsAgent and ToolsClient in the browser process. There is no direct IPC channel between inspected process and developer tools UI so all messages have to be routed through the browser process. On the side of inspected page there is ToolsAgent existing in all renderers so that we can start inspecting the page at any moment by talking to this object. On the side of developer tools renderer there is ToolsClient which is created only for RenderView that host developer tools UI. (darin: tools message representation will be later changed from id+string to just IPC::Message) Review URL: http://codereview.chromium.org/21510 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@10090 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions