These two methods are almost the same, except that the former does the wrong thing for Harmony, and the latter sets the layout manager on the host while the former doesn't.
I suspect all code calling the former really wants to call the latter. I also suspect the least code churn, and most clarity, would be achieved by eliminating the layout_utils file, moving the implementation of this function into GridLayout::CreatePanel(), and then removing the SetLayoutManager() calls from current callers.
This would have helped prevent a bug today where the newly-converted WifiConfigView tried to switch from CreatePanel() to a broken hand-rolled version of CreatePanelLayout(), and will help ensure other callers are Harmonized correctly automatically.
Elly, looks like you added this. Thoughts?
Comment 1 by pkasting@chromium.org
, Feb 1 2017