[uber page] Split up initialization of handlers from initialization of webui pages

chrome/browser/ui/webui/options/options_ui.h

Index: chrome/browser/ui/webui/options/options_ui.h
diff --git a/chrome/browser/ui/webui/options/options_ui.h b/chrome/browser/ui/webui/options/options_ui.h
index 3e6c10da0a8516ef0c05c0e8a5a03bc5bc783231..f948aba3497286787558181b4d7f2d4237bb54ee 100644
--- a/chrome/browser/ui/webui/options/options_ui.h
+++ b/chrome/browser/ui/webui/options/options_ui.h
@@ -35,6 +35,9 @@ class OptionsPageUIHandler : public content::WebUIMessageHandler,
   // This will be called only once.
   virtual void Initialize() {}
 
+  // Actually sends down values after initialization to the webui page.

[Evan Stade, 2012/03/13 20:44:50]

expand comment to highlight differences between this and initialize()

[csilv, 2012/03/13 20:59:49]

nit: remove the word "Actually".

[Dan Beam, 2012/03/13 23:01:45]

Done.

[Dan Beam, 2012/03/13 23:01:45]

Done.

+  virtual void SendPageValues() {}

[Evan Stade, 2012/03/13 20:44:50]

I am not too keen on this name. How about:

RefreshPageState()

UpdatePageState()

etc.

Or, you could change the two functions to be

InitializeHandler/InitializePage instead of Initialize/SendPageValues

[csilv, 2012/03/13 20:59:49]

I had the same reaction to the method name.

I really like Evan's suggestion to use InitializeHandler/InitializePage

[Dan Beam, 2012/03/13 23:01:45]

Done.

+
   // Uninitializes the page.  Called just before the object is destructed.
   virtual void Uninitialize() {}