Get rid of a bunch of view_messages.h includes from chrome by making the TabContentsObserver inte...

content/browser/intents/intent_injector.cc

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/browser/intents/intent_injector.h"
 
 #include "base/command_line.h"
 #include "base/logging.h"
 #include "base/string16.h"
 #include "content/browser/renderer_host/render_view_host.h"
 #include "content/browser/tab_contents/tab_contents.h"
+#include "content/common/intents_messages.h"
 #include "content/public/common/content_switches.h"
-#include "ipc/ipc_message_macros.h"
 #include "webkit/glue/web_intent_data.h"
 #include "webkit/glue/web_intent_reply_data.h"
 
 IntentInjector::IntentInjector(TabContents* tab_contents)
     : TabContentsObserver(tab_contents),
       intent_id_(0) {
   DCHECK(tab_contents);
 }
 
 IntentInjector::~IntentInjector() {
@@ skipping 23 matching lines @@
 
   SendIntent();
 }
 
 void IntentInjector::RenderViewCreated(RenderViewHost* host) {
   SendIntent();
 }
 
 void IntentInjector::DidNavigateMainFrame(
     const content::LoadCommittedDetails& details,
-    const ViewHostMsg_FrameNavigate_Params& params) {
+    const content::FrameNavigateParams& params) {
   SendIntent();
 }
 
 // TODO(gbillock): The "correct" thing here is for this to be a
 // RenderViewHostObserver, and do this on RenderViewHostInitialized. There's no
 // good hooks for attaching the intent to such an object, though. All RVHOs get
 // made deep inside tab contents initialization. Idea: propagate out
 // RenderViewHostInitialized to a TabContentsObserver latch? That still looks
 // like it might be racy, though.
 void IntentInjector::SendIntent() {
@@ skipping 30 matching lines @@
 
   if (source_tab_.get() != NULL) {
     // Swap before use since sending this message may cause
     // TabContentsDestroyed to be called.
     scoped_ptr<IPC::Message::Sender> sender;
     sender.swap(source_tab_);
     sender->Send(new IntentsMsg_WebIntentReply(
         0, reply_type, data, intent_id));
   }
 }