diff options
| author | yurys@google.com <yurys@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-02-26 09:13:01 +0000 |
|---|---|---|
| committer | yurys@google.com <yurys@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-02-26 09:13:01 +0000 |
| commit | 503683f23ea6fe3eb728f2d09f81f2603ffc7d6f (patch) | |
| tree | f9bb89d453f8d1dbd4689f0d14c477ca10e2356f /chrome/browser/browser.vcproj | |
| parent | c8c4f954af8b55d12a3d76a0ef41def31594aceb (diff) | |
| download | chromium_src-503683f23ea6fe3eb728f2d09f81f2603ffc7d6f.zip chromium_src-503683f23ea6fe3eb728f2d09f81f2603ffc7d6f.tar.gz chromium_src-503683f23ea6fe3eb728f2d09f81f2603ffc7d6f.tar.bz2 | |
Developer tools messages are forwarded as wrapped IPC::Messages(previously they were represented as int type+string body).
I stole IPC::Message serialization code from jam's CL(http://codereview.chromium.org/20413).
jam: please look at message forwarding code. When tools messages are send from browser to renderer they are also wrapped(unlike worker messages which are unwrapped and sent as is). It allows to describe developer tools messages in its own file instead of putting all of them into render_messages_internal.h
brettw: please check if it's OK to have ForwardMessageToToolsClient in WebContentsView
Review URL: http://codereview.chromium.org/21540
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@10455 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/browser.vcproj')
| -rw-r--r-- | chrome/browser/browser.vcproj | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/chrome/browser/browser.vcproj b/chrome/browser/browser.vcproj index 317ed07..f618fbe 100644 --- a/chrome/browser/browser.vcproj +++ b/chrome/browser/browser.vcproj @@ -1490,6 +1490,14 @@ > </File> <File + RelativePath=".\dom_ui\dev_tools_ui.cc" + > + </File> + <File + RelativePath=".\dom_ui\dev_tools_ui.h" + > + </File> + <File RelativePath=".\dom_ui\dom_ui.cc" > </File> |