Friday, 29 August 2014
- Re: Ambient light API redesign
- Re: Ambient light API redesign
- Re: Last Call of Battery API published, LC ends 2 October 2014
Thursday, 28 August 2014
Tuesday, 26 August 2014
- Re: Ambient light API redesign
- Re: Ambient light API redesign
- Re: Ambient light API redesign
- Re: Ambient light API redesign
- Re: Ambient light API redesign
- [light] Update - not requesting CR transition for Ambient Light given new implementer feedback
- DAP-ISSUE-170: light levels are not retrievable until a change causes the devicelight event to fire. [Ambient Light Events API]
- Re: Ambient light API redesign
- Re: Ambient light API redesign
- Ambient light API redesign
Monday, 25 August 2014
- [battery] CfC concluded: publish new LC draft of Battery API
- CfC concluded: publish CR drafts of HTML Media Capture, Ambient Light Events, and the Vibration API
Friday, 22 August 2014
- SAME 2014@NORDCHI - Ambient & Smart Media Usability, Interaction, and Media Technologies - 2nd SEPTEMBER 2014 (extended)
- Neo Ubimedia MindTrek Award - 31st August 2014 - THE competition for pervasive/ubiquitous/ambient 'minded'...
- Re: Vibration test update (Re ACTION-701: DAP testing status)
- RE: Vibration test update (Re ACTION-701: DAP testing status)
Thursday, 21 August 2014
- Wake Lock FPWD publication plan, Re: [minutes] draft minutes from DAP 2014-08-21 call
- [minutes] draft minutes from DAP 2014-08-21 call
Wednesday, 20 August 2014
- Re: CfC: publish new LC draft of Battery API, respond by 21 August 2014
- Re: CfC: publish CR drafts of HTML Media Capture, Ambient Light Events, and the Vibration API, respond by 21 August 2014
Tuesday, 19 August 2014
Monday, 18 August 2014
Friday, 15 August 2014
Tuesday, 12 August 2014
- Re: Work on new charter? (was: Call for potential DAP charter additions - please respond by 7 July 2014)
- Re: Plan to progress "wake lock"/"standby API"
- Work on new charter? (was: Call for potential DAP charter additions - please respond by 7 July 2014)
Monday, 11 August 2014
- RE: publish new LC draft of Battery API, respond by 21 August 2014
- RE: DAP-ISSUE-166: Should getBattery() always return the same promise?
- Re: DAP-ISSUE-166: Should getBattery() always return the same promise?
- RE: DAP-ISSUE-166: Should getBattery() always return the same promise?
- CfC: publish new LC draft of Battery API, respond by 21 August 2014
- Re: Plan to progress "wake lock"/"standby API"
- Plan to progress "wake lock"/"standby API"
- Re: DAP-ISSUE-169: Battery API needs to be more event driven and async, less device centric. [Battery Status API]
- Re: DAP-ISSUE-166: Should getBattery() always return the same promise?
- Re: DAP-ISSUE-168: getBattery() vs. requestBattery() pattern [Battery Status API]
Friday, 8 August 2014
- RE: DAP-ISSUE-168: getBattery() vs. requestBattery() pattern [Battery Status API]
- Re: FYI: Summary of resources updated for 1 August 2014 Process
- Re: DAP-ISSUE-169: Battery API needs to be more event driven and async, less device centric. [Battery Status API]
- Re: DAP-ISSUE-169: Battery API needs to be more event driven and async, less device centric. [Battery Status API]
- Re: DAP-ISSUE-169: Battery API needs to be more event driven and async, less device centric. [Battery Status API]
- Re: DAP-ISSUE-169: Battery API needs to be more event driven and async, less device centric. [Battery Status API]
- Re: DAP-ISSUE-168: getBattery() vs. requestBattery() pattern [Battery Status API]
- Re: DAP-ISSUE-166: Should getBattery() always return the same promise?
- Re: DAP-ISSUE-167: Should Promises be used in Battery API [Battery Status API]
- Re: DAP-ISSUE-167: Should Promises be used in Battery API [Battery Status API]
- Re: DAP-ISSUE-166: Should getBattery() always return the same promise?
- Re: DAP-ISSUE-168: getBattery() vs. requestBattery() pattern [Battery Status API]
- Re: Vibration test update (Re ACTION-701: DAP testing status)
- [battery] Cordova's feedback on the promise-based API (was: DAP-ISSUE-169)
Thursday, 7 August 2014
- DAP-ISSUE-169: Battery API needs to be more event driven and async, less device centric. [Battery Status API]
- CfC: publish CR drafts of HTML Media Capture, Ambient Light Events, and the Vibration API, respond by 21 August 2014
- RE: Vibration spec and Cordova integration update
- draft minutes from today's teleconference, 7 Aug 2014
- Re: FYI: Summary of resources updated for 1 August 2014 Process
- FYI: Summary of resources updated for 1 August 2014 Process
Wednesday, 6 August 2014
Tuesday, 5 August 2014
Monday, 4 August 2014
- Re: Vibration spec and Cordova integration update
- [admin] Agenda - DAP Distributed Meeting 7 August 2014
- [battery] Battery Issue summary and status
- DAP-ISSUE-168: getBattery() vs. requestBattery() pattern [Battery Status API]
- DAP-ISSUE-167: Should Promises be used in Battery API [Battery Status API]
- DAP-ISSUE-166: Should getBattery() always return the same promise?
- DAP-ISSUE-165: Clarify language around multiple batteries [Battery Status API]
- progressing to CR for HTML Media Capture, Ambient Light Events, and Vibration API
- Re: Vibration spec and Cordova integration update