diff options
| author | ben@chromium.org <ben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-14 21:52:13 +0000 |
|---|---|---|
| committer | ben@chromium.org <ben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-14 21:52:13 +0000 |
| commit | 2eca549205a7404aa5e9c9c978b7f3a1ea2f36d4 (patch) | |
| tree | 309b93e2e92d498b25ff38d509e0445e0c28412b /o3d | |
| parent | 0751ddc6d5451dbc6a80392b22d24deda93e0e79 (diff) | |
| download | chromium_src-2eca549205a7404aa5e9c9c978b7f3a1ea2f36d4.zip chromium_src-2eca549205a7404aa5e9c9c978b7f3a1ea2f36d4.tar.gz chromium_src-2eca549205a7404aa5e9c9c978b7f3a1ea2f36d4.tar.bz2 | |
Move TabContentsViewWin and RenderViewContextMenu*Win to browser/views/tab_contents
They are dependent on the views API (WidgetWin, Menu2, SadTabView, etc etc) so this makes sense.
As a follow-on step, I will create a new tab_contents_view_gtk.cc/h in browser/views/tab_contents as well, so TOOLKIT_VIEWS is not exposed to bustage introduced from the non-TOOLKIT_VIEWS version of this file as it is now. I cannot have two files called "tab_contents_view_gtk" in the same directory (browser/tab_contents). Mimicking TabContentsViewWin, TOOLKIT_VIEWS TabContentsViewGtk will subclass WidgetGtk, use browser/views/sad_tab_view and utilize RenderViewContextMenuWin which is now cross platform.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/126099
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18368 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'o3d')
0 files changed, 0 insertions, 0 deletions