Refactored SettingsFrontend and forwarding of calls to the backends.

chrome/browser/extensions/settings/settings_managed_frontend.cc

+// Copyright (c) 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.
+
+#include "chrome/browser/extensions/settings/settings_managed_frontend.h"
+
+#include "base/logging.h"
+#include "content/public/browser/browser_thread.h"
+
+using content::BrowserThread;
+
+namespace extensions {
+
+SettingsManagedFrontend::SettingsManagedFrontend(Profile* profile) {}

[not at google - send to devlin, 2012/07/18 07:46:18]

so I presume you'll be using the Profile for something later then :)

[Joao da Silva, 2012/07/18 21:40:25]

Yep :-) profile->GetPolicyService() is where the stuff comes from later.

[not at google - send to devlin, 2012/07/19 06:43:17]

Is it possible to only inject the PolicyService then, not the whole Profile?
Minimal dependencies, and all that.

[Joao da Silva, 2012/07/19 11:26:04]

Sure, done.

+
+SettingsManagedFrontend::~SettingsManagedFrontend() {}
+
+void SettingsManagedFrontend::RunWithStorage(const Extension* extension,
+                                             const StorageCallback& callback) {
+  DCHECK(BrowserThread::CurrentlyOn(BrowserThread::UI));
+  NOTREACHED() << "Not implemented yet.";
+  callback.Run(NULL);
+}
+
+void SettingsManagedFrontend::DeleteStorageSoon(
+    const std::string& extension_id) {
+  DCHECK(BrowserThread::CurrentlyOn(BrowserThread::UI));
+  // Not implemented yet.
+}
+
+}  // namespace extensions