aboutsummaryrefslogtreecommitdiff
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
...
* | configurable haptic mode, part 1 of 3: add haptic feedback mode to the ↵Charles Kerr2014-07-313-0/+3
| | | | | | | | GSettings schema and to our Settings object
* | drop the ubuntu-application-api middleman and call usensorsd directly: ↵Charles Kerr2014-07-311-0/+4
| | | | | | | | ua_sensors_haptic_new() crashes on desktop and ua_sensors_haptic_vibrate_once() makes blocking dbus calls.
* | in indicator::noficiations::Haptic, better naming of the Mode enumCharles Kerr2014-07-311-2/+5
| |
* | sync with lp:~charlesk/indicator-datetime/notification-refactorCharles Kerr2014-07-311-5/+4
|\|
| * sync with trunkCharles Kerr2014-07-301-0/+1
| |\
| * | fix doxygen commentsCharles Kerr2014-07-301-5/+3
| | |
* | | initial draft of haptic feedback when alarms playCharles Kerr2014-07-301-0/+57
|/ /
* | move Snap's guts into an Impl classCharles Kerr2014-07-301-4/+2
| |
* | copyediting: comments, use anonymous namespaceCharles Kerr2014-07-271-2/+3
| |
* | make close return void instead of bool, because after all what more can you ↵Charles Kerr2014-07-271-2/+2
| | | | | | | | do if the call fails? What's the point?
* | refactor the Notifications / sound / awake codeCharles Kerr2014-07-268-18/+274
| |
* | when a Snap object is destructed, delete any active Popups that it owns. ↵Charles Kerr2014-07-241-1/+6
| | | | | | | | This cleaner shutdown doesn't have any effect in production, but is needed to shut down the bus cleanly in the tests.
* | move the powerd and screen bus name, path, and interface strings into ↵Charles Kerr2014-07-231-2/+12
|/ | | | dbus-shared
* use unsigned ints for the alarm volume, duration propertiesCharles Kerr2014-06-271-2/+2
|
* Design prefers to have a volume slider instead of presets, so remove the ↵Charles Kerr2014-06-262-11/+1
| | | | AlarmVolume enum and replace it with an int range.
* Expose the alarm settings via dbus properties.Charles Kerr2014-06-261-1/+2
|
* Add Exporter's implementation to an Impl file because I'm about to shovel ↵Charles Kerr2014-06-261-19/+7
| | | | more methods and fields in there.
* in the snap decision code, handle sound custom loop durationsCharles Kerr2014-06-241-1/+4
|
* add GSettings support for specifying an alarm loop durationCharles Kerr2014-06-243-0/+3
|
* add support for per-alarm ringtone sounds set in EDS via ↵Charles Kerr2014-06-231-0/+1
| | | | E_CAL_COMPONENT_ALARM_AUDIO
* in the snap decision code, handle custom sounds and volume levels.Charles Kerr2014-06-231-1/+5
|
* add GSettings support for specifying a default alarm sound and default alarm ↵Charles Kerr2014-06-233-0/+16
| | | | volume.
* in SimpleAlarmQueue, the 'alarms we don't want to trigger' list needs to be ↵Charles Kerr2014-06-101-1/+1
| | | | composed of uid + timestamp. Keying off of only timestamp doesn't work because UIDs can be recycled as users edit and reuse alarms.
* in alarm-queue-simple, call requeue() if time skew is detected.Charles Kerr2014-06-101-1/+1
|
* in date-time.h, remove unnecessary get() call. (h/t ted)Charles Kerr2014-06-101-1/+1
|
* prefer to use ubuntu-platform-hardware-api for wakeups when possible s.t. ↵Charles Kerr2014-04-247-29/+260
|\ | | | | | | user-defined alarms/appointments can wake up the phone from sleep to give a snap decision.
| * hw alarmsCharles Kerr2014-04-247-23/+254
| |
| * rename 'clock-watcher' as 'alarm-queue' because the former name isn't very ↵Charles Kerr2014-04-241-10/+10
|/ | | | informative.
* remove unused field Appointment.is_dailyCharles Kerr2014-04-151-1/+0
|
* remove unused field Appointment.is_eventCharles Kerr2014-04-151-1/+0
|
* make the phone and desktop actions more consistent with each other; eg, ↵Charles Kerr2014-03-222-15/+24
| | | | 'indicator.desktop.open-calendar-app' + 'indicator.phone.open-calendar-app'
* Don't list an 'Add Event…' button if there's not a calendar app availableCharles Kerr2014-03-092-0/+2
|\
| * In the Desktop profile, don't show the 'Add Event…' button if evolution ↵Charles Kerr2014-03-062-0/+2
| | | | | | | | can't be launched.
* | don't connect to EDS when running in the greeter.Charles Kerr2014-03-094-28/+129
| |
* | decouple the planner's states; need three separate sets: upcoming-now (for ↵Charles Kerr2014-03-099-42/+285
| | | | | | | | alarms in the current time), upcoming-calendar (to show events coming from the selected calendar date), and calendar-month (all the appointments in the month displayed in the menu).
* | in EdsPlanner, use a Timezone instead of Timezones objectCharles Kerr2014-03-091-2/+2
| |
* | use the timezones object to set the ECalComponent's default timezone. This ↵Charles Kerr2014-02-261-1/+3
|/ | | | is needed to properly handle the 'floating' dates in the alarms
* another pass at removing alarms from the menu once they're no longer ↵Charles Kerr2014-02-051-0/+3
| | | | upcoming. This version fixes the header's icon as well.
* revert r400; we can't block alarms by UID because that would hide recurring ↵Charles Kerr2014-02-051-2/+0
| | | | alarms
* remove alarms from the menu once they've been shown in a snap decision.Charles Kerr2014-02-051-0/+2
|
* Add audio notitication when the alarm is triggered. Add a manual test to ↵Charles Kerr2014-02-041-1/+6
| | | | tests/ to trigger a snap decision.
* use the appointment's beginning time in the title of the alarm Snap DecisionCharles Kerr2014-02-041-7/+2
|
* pin the planner's upcoming appointments to the live clock time, rather than ↵Charles Kerr2014-02-041-2/+3
| | | | the calendar's time, so that they always update correctly in real-time
* add header file which should have been bzr add'ed last commitCharles Kerr2014-02-031-0/+51
|
* from alarm dev branch: add the alarm watcher and its unit testsCharles Kerr2014-02-021-0/+72
|
* copyediting: don't use camelCaseFunctionNames() in timezones-fileCharles Kerr2014-02-021-2/+2
|
* copyediting: as per review, use name_of_thing() instead of ↵Charles Kerr2014-01-304-16/+16
| | | | get_name_of_thing() or getNameOfThing()
* following on the review comment covered in the last commit, use ↵Charles Kerr2014-01-305-13/+13
| | | | shared_ptr<const X> instead of shared_ptr<X> where possible.
* as per review, there were a few places that accidentally passed a ↵Charles Kerr2014-01-302-3/+3
| | | | shared_ptr<X>& instead of a const shared_ptr<X>&
* as per review, constify getters where possible. This isn't always possible ↵Charles Kerr2014-01-302-2/+1
| | | | due to system APIs asking for non-const pointers.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 21:01:42 +0000