[ios clean] Creates ToolbarWebState Mediator

ios/clean/chrome/browser/ui/toolbar/toolbar_web_state_consumer.h

Index: ios/clean/chrome/browser/ui/toolbar/toolbar_web_state_consumer.h
diff --git a/ios/clean/chrome/browser/ui/toolbar/toolbar_web_state_consumer.h b/ios/clean/chrome/browser/ui/toolbar/toolbar_web_state_consumer.h
new file mode 100644
index 0000000000000000000000000000000000000000..95acc1fa5aeb5dfc9f88ac823d080ba0069bc15d
--- /dev/null
+++ b/ios/clean/chrome/browser/ui/toolbar/toolbar_web_state_consumer.h
@@ -0,0 +1,17 @@
+// Copyright 2017 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 IOS_CLEAN_CHROME_BROWSER_UI_TOOLBAR_TOOLBAR_WEB_STATE_CONSUMER_H_
+#define IOS_CLEAN_CHROME_BROWSER_UI_TOOLBAR_TOOLBAR_WEB_STATE_CONSUMER_H_
+
+#import <UIKit/UIKit.h>
+
+// ToolbarWebStateConsumer sets the current appeareance of the Toolbar based on

[edchin, 2017/02/21 07:56:11]

nit: spelling. appearance.

[sczs, 2017/02/21 17:28:27]

Done.

+// WebState information provided by this protocol.
+@protocol ToolbarWebStateConsumer

[marq (ping after 24h), 2017/02/21 12:04:24]

The general model I'd like to adopt is that the view controller defines a
coordinator protocol for all of the properties it needs to be provided with.
Those shouldn't be connected to any particular data source. The mediator's job
is to take one or more data sources and combine information and events from them
into updates for the consumer.

With that in mind, this should just be 'ToolbarConsumer', and the mediator will
just be 'ToolbarMediator'. The mediator will happen to accept a webState as its
input, but that's essentially an implementation detail. 

[sczs, 2017/02/21 17:28:27]

Done.

+// Sets the text for a label appearing in the center of the toolbar.
+- (void)setCurrentPageText:(NSString*)text;
+@end
+
+#endif  // IOS_CLEAN_CHROME_BROWSER_UI_TOOLBAR_TOOLBAR_WEB_STATE_CONSUMER_H_