Makoto Onuki 79d4a2d9e1 Make use of the retaining-loader feature. ... Don't use restartLoader(). Use initLoader() with stopLoader() when necessary. This allows us to make use of LoaderManager's "retaining" feature. i.e. We won't have to requery when the screen orientation changes. Also, don't start loading in onStart(). Fragment manager seems to kick exisiting loaders after onStart(), so you'll end up getting onLoadFinished() twice. (Looks like I got unluck with this--there was no strong reason to start loading in onStart rather than onResume, but I think we can leave other fragments as-is as long as they don't use loaders.) Seems to be working. Change-Id: Ib4f72098bd0fcbfce284ae6e16055d20ee410cf3		2010-08-12 11:31:14 -07:00
assets
docs
images
res	Implement "account settings"/"add account"	2010-08-10 11:08:36 -07:00
src	Make use of the retaining-loader feature.	2010-08-12 11:31:14 -07:00
tests	Fragmentize AccountSettings	2010-08-09 10:36:50 -07:00
.classpath
.project
Android.mk	add filter for emma code coverage	2010-06-17 11:25:07 -07:00
AndroidManifest.xml	Make Welcome launch MessageListXL	2010-08-05 13:58:20 -07:00
CleanSpec.mk	Add an empty CleanSpec.mk	2010-03-08 18:05:00 -08:00
MODULE_LICENSE_APACHE2
NOTICE
proguard.flags	Fragmentize AccountSettings	2010-08-09 10:36:50 -07:00
remove-exchange-support.sh	Remove exchange readme and update script	2010-02-04 13:09:34 -08:00