CC: Plumb LayerSettings parameter for cc::Layer construction.

cc/trees/layer_tree_settings.cc

Index: cc/trees/layer_tree_settings.cc
diff --git a/cc/trees/layer_tree_settings.cc b/cc/trees/layer_tree_settings.cc
index d2c3bda2b9c45c1340f5276ff59dd8b85855b1dd..529f63eaf03c8caee04c18276cc84602c87e0192 100644
--- a/cc/trees/layer_tree_settings.cc
+++ b/cc/trees/layer_tree_settings.cc
@@ -13,6 +13,12 @@
 
 namespace cc {
 
+LayerSettings::LayerSettings() : use_compositor_animation_timelines(false) {

[enne (OOO), 2015/05/18 21:49:49]

Are you expecting more settings in the future? Does this bool have to be a ctor
parameter to Layer?

[loyso (OOO), 2015/05/19 01:03:44]

A bit of context/historical background: It's started here
https://codereview.chromium.org/1101823002/patch/120001/130002

Strictly IMHO:

1) No, I don't expect more settings in the future, especially in the context of
my project (cc animations). cc::Layer constructor will be eventually empty:
https://codereview.chromium.org/1130043003/diff/20001/cc/layers/layer.cc

Moreover, in a long term cc::Layers system is deprecated in favor of
DisplayLists (Slimming Paint).

2) No, that bool hasn't to be passed intro constructor if we choose
RegisterForAnimations approach. (Patch Set#7
https://codereview.chromium.org/1101823002/#ps120001)

+}
+
+LayerSettings::~LayerSettings() {
+}
+
 LayerTreeSettings::LayerTreeSettings()
     : impl_side_painting(false),
       raster_enabled(true),
@@ -69,8 +75,7 @@ LayerTreeSettings::LayerTreeSettings()
       use_display_lists(false),
       use_cached_picture_in_display_list(true),
       verify_property_trees(false),
-      gather_pixel_refs(false),
-      use_compositor_animation_timelines(false) {
+      gather_pixel_refs(false) {
 }
 
 LayerTreeSettings::~LayerTreeSettings() {}