cc: Start using raster/eviction iterators in tile manager

cc/layers/picture_layer_impl.h

 // Copyright 2012 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.
 
 #ifndef CC_LAYERS_PICTURE_LAYER_IMPL_H_
 #define CC_LAYERS_PICTURE_LAYER_IMPL_H_
 
 #include <string>
 #include <vector>
 
@@ skipping 21 matching lines @@
   class CC_EXPORT LayerRasterTileIterator {
    public:
     LayerRasterTileIterator();
     LayerRasterTileIterator(PictureLayerImpl* layer, bool prioritize_low_res);
     ~LayerRasterTileIterator();
 
     Tile* operator*();
     LayerRasterTileIterator& operator++();
     operator bool() const;
 
+    bool HasTilesRequiredForActivation() const;

[reveman, 2014/05/20 23:01:00]

Everything related to HasTilesRequiredForActivation is unnecessary once
https://codereview.chromium.org/287643004/ lands, right?

[vmpstr, 2014/05/27 22:41:32]

That's correct. I'm keeping it here just for testing, but it all goes away with
the activation patch. One concern with rebasing is that I'll probably just end
up calling the check after every rasterizer notification, since I have no other
hints to determine whether it's a good time to activate.

[reveman, 2014/05/28 16:04:12]

See my comment on latest patch.

+
    private:
     enum IteratorType { LOW_RES, HIGH_RES, NUM_ITERATORS };
 
     PictureLayerImpl* layer_;
 
     struct IterationStage {
       IteratorType iterator_type;
       TilePriority::PriorityBin tile_type;
     };
 
@@ skipping 171 matching lines @@
   gfx::Size viewport_size_for_tile_priority_;
   gfx::Transform screen_space_transform_for_tile_priority_;
 
   friend class PictureLayer;
   DISALLOW_COPY_AND_ASSIGN(PictureLayerImpl);
 };
 
 }  // namespace cc
 
 #endif  // CC_LAYERS_PICTURE_LAYER_IMPL_H_