[Mac] Organize some files into chrome/browser/ui/cocoa/content_settings/....

[Mac] Organize some files into chrome/browser/ui/cocoa/content_settings/.

BUG=none
TEST=none
R=thakis

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=71958

[Nico, 2011-01-20 15:46:22]

Are you planning to do the same for win / linux? I believe the content settings
stuff is in options/ and maybe autocomplete/ over there atm.

[Robert Sesek, 2011-01-20 15:58:13]

On 2011/01/20 15:46:22, Nico wrote:
> Are you planning to do the same for win / linux? I believe the content
settings
> stuff is in options/ and maybe autocomplete/ over there atm.

I wasn't, no. I've already moved preferences part of content settings lives to
options/. I don't think autocomplete/ makes any sense for this stuff. These
files are all related to the bubbles, so I think this is the right place for
them. The other platforms' bubble stuff lives in their top-level directory
because they have fewer files.

[Nico, 2011-01-20 16:06:08]

LG with green mac_rel --clobber try run.

http://codereview.chromium.org/6294008/diff/1/chrome/browser/ui/cocoa/content...
File chrome/browser/ui/cocoa/content_settings/OWNERS (right):

http://codereview.chromium.org/6294008/diff/1/chrome/browser/ui/cocoa/content...
chrome/browser/ui/cocoa/content_settings/OWNERS:3: thakis@chromium.org
I wonder if this OWNERS file business means that longer term we'll end up with
directories like

c/b/ui/feature
c/b/ui/feature/cocoa
c/b/ui/feature/gtk
c/b/ui/feature/views

because it's a bit strange that the people who wrote the feature model code
can't change the corresponding view code by default. Anyway :-)

[Robert Sesek, 2011-01-20 16:13:50]

On 2011/01/20 16:06:08, Nico wrote:
> LG with green mac_rel --clobber try run.

http://build.chromium.org/p/tryserver.chromium/builders/mac_rel/builds/54

> chrome/browser/ui/cocoa/content_settings/OWNERS:3: mailto:thakis@chromium.org
> I wonder if this OWNERS file business means that longer term we'll end up with
> directories like
> 
> c/b/ui/feature
> c/b/ui/feature/cocoa
> c/b/ui/feature/gtk
> c/b/ui/feature/views
> 
> because it's a bit strange that the people who wrote the feature model code
> can't change the corresponding view code by default. Anyway :-)

I think Peter brought that up a while ago, and I understand that point. But I
think the counterpoint is that people who write the models aren't necessarily
familiar with a given platform's semantics, so they shouldn't own the
controller/view part. And at least during the porting effort, the two people
usually weren't the same.