| 76472ae40cd55d17edb0420e8fc2a7bae60c50de |
|
13-Feb-2014 |
Tony Mantler <nicoya@google.com> |
Merge setup fragments under a single activity
Change-Id: I10cf8bb9f6bc1a26ea97ae664f0196ae9e9493b5
/packages/apps/Email/src/com/android/email/activity/setup/AccountSetupActivity.java
|
| 9c8c471f971f9c8e40002503a0799ce56c5bfd76 |
|
06-Dec-2013 |
Tony Mantler <nicoya@google.com> |
Convert SetupData into a retained fragment
This will keep it from being recreated quite as much while off-thread tasks are possibly mutating it.
Change-Id: Ic9873489906339c33a76b8a600c0fc28016debc4
/packages/apps/Email/src/com/android/email/activity/setup/AccountSetupActivity.java
|
| c80688903d815b573c276fb00ba8f123cbdf622d |
|
23-Nov-2013 |
Tony Mantler <nicoya@google.com> |
Line length
Change-Id: I50cf8aef2de5ec490cc081a1c67e6f3727b15cb1
/packages/apps/Email/src/com/android/email/activity/setup/AccountSetupActivity.java
|
| 9d3e01c589e1f281941cff9abc59aba0b0f33e78 |
|
27-Sep-2013 |
Martin Hibdon <mhibdon@google.com> |
Set the client cert from AccountSetup
b/9661767
Change-Id: I292ff5e190ed56077a04e37869e18a46f5473985
/packages/apps/Email/src/com/android/email/activity/setup/AccountSetupActivity.java
|
| 26cd5e024c6af8ff9c8558325dd0930c9aacb370 |
|
31-Aug-2013 |
Tony Mantler <nicoya@google.com> |
Don't store the account creation/modificaiton state in a singleton
b/10460757
Change-Id: I7f0bea69f843f9061d1cfa9277c99d36705aceaf
/packages/apps/Email/src/com/android/email/activity/setup/AccountSetupActivity.java
|
| 560bfadc3151f7a06f3b06e9a6c92cfa534c63ec |
|
26-May-2013 |
Scott Kennedy <skennedy@google.com> |
Unify LogTag
There is now only one LogTag class. The static initializer of
GmailApplication (existing) and EmailApplication (new) will now set
the log tag to "Gmail" and "Email", respectively. Up until that code
is run, it will be "UnifiedEmail".
"setprop log.tag.Gmail VERBOSE" (or .Email) will trigger all logs to
be printed as long as they go through LogUtils, regardless of what tag
is used by that individual log. This lets us still turn on logging
everywhere in one command, but also lets us use more descriptive tags
(like the class name).
And since we no longer have three com.android.mail.utils.LogTag
classes, builds will be much easier.
Also, we now use LogUtils everywhere.
Change-Id: I55f1c7a66ce50ead54877a13e40256422a56dc39
/packages/apps/Email/src/com/android/email/activity/setup/AccountSetupActivity.java
|
| 5920989bdec326ff3e9d70d6a530d8b99a98f5c7 |
|
24-Feb-2011 |
Todd Kennedy <toddke@google.com> |
Fix NPE when restoring setup activity
If the setup activity ever needs to restore itself after being killed, we were
restoring the Activity object's state (i.e. rebuilding the UI) before we
restored the state of our class. Since the Activity necessarily depends upon
our object's state, Bad Things can [and will] happen.
The solution is simple -- save our object's state last, but, restore our state
first.
bug 3476039
Change-Id: I623f1938c2e0f50d660708a7a7ac3eeb4a8f9090
/packages/apps/Email/src/com/android/email/activity/setup/AccountSetupActivity.java
|
| e6cc662abc0b5fffe223cda5e980b4f05a4e91dd |
|
08-Jul-2010 |
Marc Blank <mblank@google.com> |
Use AccountManager for POP/IMAP; refactor setup classes
There are two major, interrelated parts to this CL:
1) Clean up the activities to reduce the use of Intents to pass
information between activities; instead, we use a common
SetupData structure that automatically saved/restored as necessary
during the setup flow. A fair amount of code and inconsistent
use of Bundle extras has been eliminated in the process.
* Create SetupData structure, setters/getters, and initialization
methods to simplify the preservation of state during setup flow
* Remove all state/flow extras from Intents; Intents now only
specify the Activity to be started, which should greatly simplify
the transition to Fragments.
* Remove all state/flow fields from Activities
* Modify existing setup activity unit tests and confirm tests pass
2) Create AccountManager accounts for POP/IMAP email accounts to
provide consistency in user experience. Also, internal flows are
now identical as between account types.
* Move account reconciliation from SyncManager to MailService, so
that reconciliation is consistent between email and exchange
accounts; move unit tests as appropriate
* Add a "Sync Email" setting for POP/IMAP/EAS
* Change MailService to respect the "Sync Email" setting in
Settings -> Accounts & sync
* Create PopImapSyncAdapterService to handle manual POP/IMAP sync as
requested by SyncManager; add EmailSyncAdapterService to perform
the same function for EAS
* Use new PopImapAuthenticatorService to add AccountManager accounts
for POP/IMAP accounts; setup appropriate stanzas in AndroidManifest
and add related xml files
* Update AccountSettings to use SetupData
Miscellaneous other changes:
* Only allow valid port numbers in incoming/outgoing setup
Bug: 1712475
Change-Id: Ibdac52fb2c5578b86bf3992ddb1acd10f162391a
/packages/apps/Email/src/com/android/email/activity/setup/AccountSetupActivity.java
|