Replace TabContentsViewGtk with TabContentsViewViews as part of the ongoing

chrome/browser/renderer_host/backing_store_x.h

Index: chrome/browser/renderer_host/backing_store_x.h
diff --git a/chrome/browser/renderer_host/backing_store_x.h b/chrome/browser/renderer_host/backing_store_x.h
index e6a73a75ddde1f60f8680d83b7fefd1c28a16d88..b79d648eaf06615b87be027d9dbb2fc2e54e7c3a 100644
--- a/chrome/browser/renderer_host/backing_store_x.h
+++ b/chrome/browser/renderer_host/backing_store_x.h
@@ -11,6 +11,11 @@
 #include "build/build_config.h"
 #include "chrome/browser/renderer_host/backing_store.h"
 
+namespace gfx {
+class Point;
+class Rect;
+}  // namespace gfx
+
 typedef struct _GdkDrawable GdkDrawable;
 class SkBitmap;
 
@@ -34,9 +39,12 @@ class BackingStoreX : public BackingStore {
   XID root_window() const { return root_window_; }
 
   // Copy from the server-side backing store to the target window
-  //   display: the display of the backing store and target window
+  //   origin: the destination rectangle origin
   //   damage: the area to copy
   //   target: the X id of the target window
+  void XShowRect(const gfx::Point &origin, const gfx::Rect& damage,
+                 XID target);
+  // As above with origin 0,0
   void XShowRect(const gfx::Rect& damage, XID target);

[brettw, 2010/11/12 21:55:51]

The style guide says not to have overloaded functions like this. I'd just change
the callers to say Point(0, 0) which is pretty easy and obvious

 
   // As above, but use Cairo instead of Xlib.