Stick windows to sides of workspaces

ash/wm/window_properties.h

Index: ash/wm/window_properties.h
diff --git a/ash/wm/window_properties.h b/ash/wm/window_properties.h
index 21d7ae9e5dfedf7dbe12bf73b0c7cfbe2b0e116a..d0a8418fdf0cbf11b30aeca087791dd339583c8d 100644
--- a/ash/wm/window_properties.h
+++ b/ash/wm/window_properties.h
@@ -98,9 +98,11 @@ ASH_EXPORT extern const aura::WindowProperty<bool>* const
 // window to the restore-bounds (false by default).
 extern const aura::WindowProperty<bool>* const kWindowRestoresToRestoreBounds;
 
+// A bitmask containing the workspace edges that the window is stuck to.

[flackr, 2013/05/01 17:34:04]

I don't think we'll have any useful behaviors for windows being "stuck" to more
than one edge. We should probably only remember the right or left and perhaps
neither if the window is touching both.

[varkha, 2013/05/18 03:06:37]

I am not sure. When the gutter appears, say on the right with the non-maximized
window moving the gutter boundary left would eventually squeeze the window to
the left of it to be stuck to both edges. In this state dragging the gutter
boundary back to the right I think should preserve the window touching both the
left edge (screen) and the right edge (gutter edge). This can now be done by
resizing the screen.
Also resizing to both right and left or docking to max-left or max-right creates
multiple edges situations that we probably want to maintain when gutter and / or
launcher size and / or visibility change.

[flackr, 2013/05/22 02:00:56]

For now, I think a window touching a gutter should not be considered "stuck". We
only want to allow one gutter at a time.

+extern const aura::WindowProperty<int>* const kWindowStuckToEdge;
+
 // True if the window is controlled by the workspace manager.
-extern const aura::WindowProperty<bool>* const
-    kWindowTrackedByWorkspaceKey;
+extern const aura::WindowProperty<bool>* const kWindowTrackedByWorkspaceKey;
 
 // Alphabetical sort.