cros: Initial structure for views-based lock.

ash/BUILD.gn

Index: ash/BUILD.gn
diff --git a/ash/BUILD.gn b/ash/BUILD.gn
index b1eee6a1f3555606d372545aef930bbe4f3688df..6888e26e74a3852e161d33e50a3a56fcfa08d90a 100644
--- a/ash/BUILD.gn
+++ b/ash/BUILD.gn
@@ -201,6 +201,10 @@ component("ash") {
     "link_handler_model.h",
     "link_handler_model_factory.cc",
     "link_handler_model_factory.h",
+    "login/views/contents_view.cc",

[James Cook, 2017/05/08 22:04:20]

Why the extra /views/ subdir? Do you anticipate that there will be code here
that isn't views?

[jdufault, 2017/05/08 23:02:34]

Yes - mojo implementations soonish for the existing webui chrome.send API calls.
Later on I'd like to migrate the login code in chrome, ie, talking to
cryptohome, here as well.

[James Cook, 2017/05/08 23:24:09]

Hrm. What do you think the other subdirectories are going to be?

If you don't think it'll be that many files, I would just throw them all under
ash/login to keep the directories from getting too deep.

I would keep ash/login/views if you think there will be an ash/login/webui
someday.

[jdufault, 2017/05/08 23:48:28]

There will be some webui code to interface with gaia, but I'm not sure it will
be enough to justify a separate directory.

I do think there will be significant chunks of non-views code though - take a
look at chrome/browser/chromeos/login/* for some of it (though that directory
also includes oobe). easy_unlock is a good candidate.

+    "login/views/contents_view.h",
+    "login/views/lock_screen.cc",
+    "login/views/lock_screen.h",
     "login_status.h",
     "magnifier/magnification_controller.cc",
     "magnifier/magnification_controller.h",