Migrating host preferences, runtime, and gestures to chromium from internal.

remoting/client/ios/host_preferences_chromium.mm

Index: remoting/client/ios/host_preferences_chromium.mm
diff --git a/remoting/client/ios/host_preferences_chromium.mm b/remoting/client/ios/host_preferences_chromium.mm
new file mode 100644
index 0000000000000000000000000000000000000000..6c9d9ebd5b95927098e4f60c4172062780d75e28
--- /dev/null
+++ b/remoting/client/ios/host_preferences_chromium.mm
@@ -0,0 +1,21 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.

[Sergey Ulanov, 2017/01/18 22:20:35]

2017

+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+

[nicholss, 2017/01/13 19:20:34]

This is an implementation for Chromium to allow the build to build without
missing symbols.

+#import "remoting/client/ios/host_preferences.h"
+
+#import "base/logging.h"
+
+namespace remoting {
+namespace ios {
+
+NSError* writeHostPreferencesToKeychain(NSData* data) {
+  return nil;

[Sergey Ulanov, 2017/01/18 22:20:35]

NOTIMPLEMENTED();

Also, would it be useful to save |data| in a static variable, which is then
returned from readHostPreferencesFromKeychain()?
That would allow to test pairing, even though the pairing info is not persisted
when the app is restarted.

[nicholss, 2017/01/18 23:21:50]

Done.
That is is a good idea. I would have to work out a way to copy the data to a
local var, and I am not sure I care to work that out at the moment but I will
add a TODO to remember to get to that when I work on testing the keychain
functionality. I am not 100% sure this implementation will be the final way we
do it. I am just modifying it in the minimum way possible to be able to get this
into chromium from internal.

+}
+
+NSData* readHostPreferencesFromKeychain() {
+  return nil;

[Sergey Ulanov, 2017/01/18 22:20:35]

NOTIMPLEMENTED()

[nicholss, 2017/01/18 23:21:50]

Done.

+}
+
+}  // namespace ios
+}  // namespace remoting