Move commit list and builder latest revisions up to ct-unexpected-failures

Tools/GardeningServer/model/ct-commit-log-mock.html

+<!--
+Copyright 2014 The Chromium Authors. All rights reserved.
+Use of this source code is governed by a BSD-style license that can be
+found in the LICENSE file.
+-->
+
+<link rel='import' href='ct-commit-log.html'>
+
+<link rel='import' href='ct-commit-mock.html'>

[abarth-chromium, 2014/07/19 02:40:04]

can we drop the ct prefix?

[ojan, 2014/07/19 02:44:22]

I thought about that, but the model is intimately tied to the components that
use it. So, if we were to move the component that depends on this model object,
we'd move the model object along with it. So, you still want namespacing, right?

I thought about using a different namespace, but concluded that it being in a
different directory was sufficient.

Certainly open to suggestions/criticisms/alternatives. This patch is by no means
intended to be the final result. Now is the right time to discuss high-level
design and/or style things related to this change, since there will be similar
followup patches once this lands (e.g. converting ct-failure-analyzer to a model
class).

[michaelpg, 2014/07/21 07:28:48]

I wouldn't mind something like
  <ct-model-commit>
just so it's clear in other components' templates which components are data and
which are UI.

Come to think of it, what does "ct" stand for?

[ojan, 2014/07/21 19:58:04]

ct == chromium-tools. In a future world in which we share code between tools,
we'll move some of these to a shared base library. Really we should be
distinguishing between ct and sm (sheriff-o-matic) already, but we can make that
change when we actually start putting the shared code in a shared place.

As to the naming, I don't feel strongly. There is no DOM in the model directory.
So, there's:
CTCommit == model
<ct-commit> == ui

We could rename the file to include model in the filename, but that seemed
redundant, e.g. model/ct-model-commit.html, model/ct-model-commit-log.html, etc.

[michaelpg, 2014/07/22 05:47:37]

Oops, I didn't realize that there actually was a ct-commit UI element as opposed
to it just holding data. In that case, this is great.

+
+<script>
+(function () {
+
+window.CTCommitLogMock = function() {
+  var log = new CTCommitLog();
+  var commit = new CTCommitMock();
+  log[commit.revision] = commit;
+  return log;
+};
+
+})();
+</script>