Move classes to //components/ntp_tiles.

components/ntp_tiles/DEPS

Index: components/ntp_tiles/DEPS
diff --git a/components/ntp_tiles/DEPS b/components/ntp_tiles/DEPS
new file mode 100644
index 0000000000000000000000000000000000000000..56b72da1d326175f56db394b4cc2879259ba6aa2
--- /dev/null
+++ b/components/ntp_tiles/DEPS
@@ -0,0 +1,17 @@
+include_rules = [
+  "+components/google/core/browser",
+  "+components/history/core/browser",
+  "+components/pref_registry",
+  "+components/prefs",
+  "+components/safe_json",
+  "+components/search_engines",
+  "+components/suggestions",
+  "+components/variations",
+  "+content/public/browser",

[sdefresne, 2016/05/24 06:36:32]

Is there plan to use this component on iOS? If yes, I would recommend removing
the dependency on //content/public/browser before moving this code into the
component. It looks like the only dependency is on content::BrowserThread which
is easy to abstract by injecting the threads into the object at creation (see
all the other layered components).

If no, what are the different embedders that will use this component?

[sfiera, 2016/05/24 12:40:15]

Our immediate plan is to use it in the desktop new tab page; we haven't made any
plans to use it on iOS. We might eventually want to, but it would be a few
quarters out at least.

[Marc Treib, 2016/05/24 12:46:35]

I guess the main blocker is that nobody on our team has experience with iOS. If
somebody from the iOS team wants to do the integration work, then I'm sure we
can make that happen in less than a few quarters :)
Not in this CL though.

+  "+google_apis",
+  "+net/base",
+  "+net/http",
+  "+net/url_request",
+  "+third_party/skia/include",
+  "+ui/gfx",
+]