[MacViews] Implement size constraints for app windows.

ui/gfx/mac/nswindow_util.h

+// Copyright 2015 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 UI_GFX_MAC_NSWINDOW_UTIL_H_
+#define UI_GFX_MAC_NSWINDOW_UTIL_H_
+
+#import <Cocoa/Cocoa.h>

[tapted, 2015/03/25 18:50:23]

nit: forward declare @class NSWindow;

[jackhou1, 2015/03/26 03:50:46]

Done.

+
+#include "ui/gfx/geometry/size.h"

[tapted, 2015/03/25 18:50:23]

nit: forward declare

[jackhou1, 2015/03/26 03:50:46]

Done.

+
+void SetFullScreenCollectionBehavior(NSWindow* window, bool allow_fullscreen);
+
+void SetResizableStyleMask(NSWindow* window, bool resizable);
+
+// Sizes refer to the content size (inner bounds).
+void ApplySizeConstraints(NSWindow* window,
+                          gfx::Size min_size,

[tapted, 2015/03/25 18:50:23]

nit: const-reference

[jackhou1, 2015/03/26 03:50:46]

Done.

Is it a rule to always pass gfx::SmallThing by const-ref? I would have thought
it'd be better to copy, do we ever do that in Chrome?

[tapted, 2015/03/30 06:33:37]

`git grep '(.*gfx::Size' -- '*.h'` has mostly const-reference

Unless it's smaller than a pointer, I don't think there are compelling upsides
to requiring the copy constructor call. And there are other downsides to
copy-constructing, like being unable to "passthrough" an argument to another
function without #including its header.

There are some other arguments around pointer-aliasing and codegen opportunities
when you actually want to modify the argument in your function, but they apply
mostly to inline functions AFAIK.

+                          gfx::Size max_size,
+                          bool can_resize,
+                          bool can_fullscreen);
+
+#endif  // UI_GFX_MAC_NSWINDOW_UTIL_H_