tree 0fb79e5d77d0ba474c4be5ff168ff5142a4feca7
parent 1e926e4233a7e88039950e5b3212b19d5a63ff5a
author Viet-Trung Luu <viettrungluu@chromium.org> 1463525390 -0700
committer Viet-Trung Luu <viettrungluu@chromium.org> 1463525390 -0700

Make ApplicationTestBase not use ApplicationImpl.

It didn't have much reason to.

This allows us to make ApplicationImpl's Application implementation
private.

My plan:
* Factor out the guts of ApplicationImpl to a new class called
  ApplicationImplBase, which would have a bunch of (possibly pure)
  virtual methods meant to be overridden. (I'd mark methods not meant to
  be overridden as |final|.)
* ApplicationImpl would (temporarily?) remain, implementing these
  methods by calling out to ApplicationDelegate.
* Convert code to just subclassing/implementing ApplicationImplBase,
  instead of ApplicationDelegate (and instantiating that class, instead
  of ApplicationImpl + their delegate).
* Once no one uses ApplicationImpl/ApplicationDelegate anymore, we can
  remove them.

R=vardhan@google.com

Review URL: https://codereview.chromium.org/1990603002 .