History log of /packages/apps/DeskClock/src/com/android/deskclock/data/SettingsModel.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
cfcf52fcb8207628ba53336b77452191d07d64ec 10-Oct-2015 James Lemieux <jplemieux@google.com> Miscellaneous Cleanup

- unused classes, methods and layouts removed
- snapshotting the user's home timezone moved into DataModel
- safeguard against multiple clicks in ShowAlarmsActivity

Change-Id: I47788aeac2c5de143e45e8671219203b2e143250
/packages/apps/DeskClock/src/com/android/deskclock/data/SettingsModel.java
6a59a7b2c034557bc8bc7481544db5cd1105a891 20-Aug-2015 James Lemieux <jplemieux@google.com> Alarms created from external intents use default ringtone

Clock recently gained the notion of "application default ringtone"
but this was ignored in favor of "system default alarm ringtone" when
creating alarms from external intents. This behavior was fixed.

A secondary cleanup moved the functionality in
RingtoneDataManager into DataModel.

Bug: 23353723
Change-Id: Id092101dc30ec6c48f59cf4f142778b08a6075de
/packages/apps/DeskClock/src/com/android/deskclock/data/SettingsModel.java
856483e7e18d5f042a338f7b3d472e28a386c4ad 18-Aug-2015 James Lemieux <jplemieux@google.com> remove requests for READ_EXTERNAL_STORAGE permission

Very late in the M release, a change was made to no longer
require the READ_EXTERNAL_STORAGE permission to view
the titles of external ring tones. Consequently, we no longer
have a reason to acquire this permission in the application.

As well, the storage of the ringtone to play for expired timers
has been moved from Utils into the DataModel.

Bug: 22919062
Change-Id: I9209cd3e6efaee1063c1c04bca15b0ea61ffc4d8
/packages/apps/DeskClock/src/com/android/deskclock/data/SettingsModel.java
34142b1d0f2445bbd606bb490dfef6c078c630ea 14-Aug-2015 James Lemieux <jplemieux@google.com> Refactor Cities (World Clocks) to use new unified DataModel

This refactoring replaces CityObj with City, an immutable description
of a city and its associated clock information. City objects are fetched
via a DataModel class that is the single point of reference for all City
data. This allows the data to be shared across the entire application.
In particular, DigitalWidgetViewsFactory, ClockFragment and
CitySelectionActivity all draw upon the same model to determine what
cities exist, which ones are selected, and what the preferred display
order shall be.

Change-Id: I7c2eaa31b596b5333213415af58a7bb46ebb370e
/packages/apps/DeskClock/src/com/android/deskclock/data/SettingsModel.java