Adding Baseframework of the ResourceManager (all hooks and observers) are being put in place with a…

athena/wm/public/window_manager_observer.h

Index: athena/wm/public/window_manager_observer.h
diff --git a/athena/wm/public/window_manager_observer.h b/athena/wm/public/window_manager_observer.h
index 216b58ceeee3e39287b67c2aa25177e96bc9e088..49ef7536c50aa3bc487ff77fcbd4b762debb1e1d 100644
--- a/athena/wm/public/window_manager_observer.h
+++ b/athena/wm/public/window_manager_observer.h
@@ -18,6 +18,9 @@ class ATHENA_EXPORT WindowManagerObserver {
 
   // Called immediately after going out of the overview mode.
   virtual void OnOverviewModeExit() = 0;
+
+  // Called after the activity order has changed.
+  virtual void OnActivityOrderHasChanged() = 0;

[Jun Mukai, 2014/08/27 01:21:19]

Should we use wm::ActivationChangeObserver instead? (see
ui/wm/public/activation_change_observer.h)

[Mr4D (OOO till 08-26), 2014/08/27 16:12:14]

Any re-ordering is of interest since "older" activities need adjusting and the
order does define that. If we would have used the container window for
organizing our activities, that could have been done through its WindowObserver
- and / or in that case we might have used the suggested
activation_change_observer and hold the activity order ourselves. However -
Oshima asked to decouple the activity order management from the window
management. Does that make sense?

[Jun Mukai, 2014/08/27 16:57:48]

I see. Makes sense.

 };
 
 }  // namespace athena