commit 3f6c104ae9c832927bdfa1626bafb7009885e7c5
author rjrjr@google.com <rjrjr@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Mon May 09 15:12:52 2011 +0000
committer rjrjr@google.com <rjrjr@google.com@8db76d5a-ed1c-0410-87a9-c151d255dfc7> Mon May 09 15:12:52 2011 +0000
tree 72267418e19a94213596a5b2e6bed6cd93ce54ec
parent a5f017a6dee0bb29c4f2e32c3a041b484ba38546

Step one in making mobilewebapp more DI friendly. The goal is to
remove all knowledge of ClientFactory from any class but the entry
point.

This gets the basic pattern in place, submitting it as a checkpoint so
that new features can appear in the right place.

In particular, introduces the App class, and elminates a lot of low
hanging ClientFactory leakage. The interesting bit will be getting it
out of the activities. And a particularly nasty spot is where
MobileWebAppShellTablet (view class) is kicking off a
TaskListActivity. That's next.

Review at http://gwt-code-reviews.appspot.com/1433801

Review by: jlabanca@google.com

git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@10163 8db76d5a-ed1c-0410-87a9-c151d255dfc7