Adding the iOS app and integration example with GlRenderer.

remoting/client/ios/app/example_view_controller.h

+// 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 REMOTING_CLIENT_IOS_APP_EXAMPLE_VIEW_CONTROLLER_H_
+#define REMOTING_CLIENT_IOS_APP_EXAMPLE_VIEW_CONTROLLER_H_
+
+#import <GLKit/GLKit.h>
+#import "remoting/client/ios/display/gl_display_handler.h"
+#include "remoting/client/ios/app_runtime.h"
+
+#include "remoting/client/software_video_renderer.h"
+#include "remoting/codec/video_encoder_verbatim.h"
+#include "remoting/proto/video.pb.h"
+#import "remoting/client/ios/client_gestures.h"
+
+@interface ExampleViewController : GLKViewController {
+ @private
+
+  // The GLES3 context being drawn too.

[joedow, 2017/01/25 23:16:28]

nit: s/too/to

[nicholss, 2017/01/26 18:00:15]

Done.

+  EAGLContext* _context;
+  remoting::ios::AppRuntime* _runtime;
+  GlDisplayHandler* displayHandler;

[joedow, 2017/01/25 23:16:28]

displayHandler needs a leading underscore (_displayHandler).

For consistency, can you update the members with trailing underscores to use
leading?

Style guide is odd as it says to prefer leading underscores but says trailing
underscores are ok to match existing code.  In this CL I've seen both.  I'm
happy with either as long as it is consistent :)

[nicholss, 2017/01/26 18:00:16]

This is really confusing to know which to use, infact bling has the same
problem. The reason for the trailing _ is the auto property magic addes a _ to
the front so _foo becomes __foo and foo_ becomes _foo_ 

Will fix to be consistent 

+  remoting::SoftwareVideoRenderer* video_renderer_;
+
+  remoting::VideoEncoderVerbatim encoder_;
+  ClientGestures* _gestures;
+}
+
+@end
+
+#endif  // REMOTING_CLIENT_IOS_APP_EXAMPLE_VIEW_CONTROLLER_H_