Implement message center on Windows

chrome/browser/ui/message_center/message_center_util.h

Index: chrome/browser/ui/message_center/message_center_util.h
diff --git a/chrome/browser/ui/message_center/message_center_util.h b/chrome/browser/ui/message_center/message_center_util.h
new file mode 100644
index 0000000000000000000000000000000000000000..4601797c1e2214c7708f9770d0214e54ce2f3da8
--- /dev/null
+++ b/chrome/browser/ui/message_center/message_center_util.h
@@ -0,0 +1,19 @@
+// 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 CHROME_BROWSER_UI_MESSAGE_CENTER_MESSAGE_CENTER_UTIL_H_
+#define CHROME_BROWSER_UI_MESSAGE_CENTER_MESSAGE_CENTER_UTIL_H_
+

[Pete Williamson, 2013/01/16 19:43:20]

General guidance - whenever something has "util" or "manager" in its name, that
is a sign that either the name is weak or the responsibilities of the class are
not well thought out.  It also invites becoming a dumping ground for other
functionality which is only loosely related (low cohesion).  Consider whether
this can be named better.  MessageCenter?  MessageCenterSingleton?
MessageCenterFactory? MessageCenterAccessor?

[dewittj, 2013/01/16 22:30:40]

I agree the name is weak.  It is modeled after the app list code which has
similar platform dependencies, and which has a file much like this one.  The
issue here was getting a static function that would link in a component build.

+namespace ui {
+class MessageCenterTrayHost;
+}
+
+namespace chrome {
+
+  // Show the message center tray widget.
+  ui::MessageCenterTrayHost* GetMessageCenterTray();
+
+}  // namespace chrome
+
+#endif  // CHROME_BROWSER_UI_MESSAGE_CENTER_MESSAGE_CENTER_UTIL_H_