Re: ISSUE-16: Gathering requirements [User Interaction API]

Perhaps of interest from a mobile device perspective a notification
can be of the form of vibration or different lights found on the phone
(Blackberrys have a bewildering array / the new Palm Pre has two nice
lights on either side of the home button to indicate different
gestures have been entered such as back/forward). Sometimes a
notification might be a beep!

So, notifications may not take the form of a modal/non-modal dialogue.



On Mon, Oct 19, 2009 at 9:09 AM, Anssi Kostiainen
<anssi.kostiainen@nokia.com> wrote:
> On 25.8.2009, at 16.29, ext Device APIs and Policy Working Group Issue
> Tracker wrote:
>>
>> ISSUE-16: Gathering requirements [User Interaction API]
>>
>> http://www.w3.org/2009/dap/track/issues/16
>
>
> It seems the ISSUE-16 has not been discussed on the list yet. To recap,
> according to the Charter deliverables section:
>
> [[
> User Interaction API, a set of APIs that gives a widget or website far
> better control of how it manifests itself on different platforms. This would
> include minimise/maximise functions, window size, alerting mechanisms etc.
> ]]
>
> Below is a summary of prior art related to "alerting mechanisms" after a
> quick scan.
>
> The getAttention() and showNotification() methods were specified in the
> earlier WDs of the Widgets A+E spec [1] but have since been removed
> presumably due scope creep and inconsistency concerns with what HTML5
> specifies(?). The notification functionality has also been in the HTML5 spec
> (see e.g. [2]) at some point, but has been removed due to lack of interest
> [3]. Summary of related specs:
>
>  - getAttention() and showNotification() in Widgets A+E [1]
>  - showNotification() in HTML5 [2]
>
> Related implementations:
>
>  - create/showNotification() in Gears [4]
>  - createPopup() in IE [5]
>  - create[HTML]Notification() in WebKit [6,7]
>
> Older discussion which pre-dates (most of) the above:
>
>   - getAttention() [8] and showNotification() [9] at Bugzilla@Mozilla
>
> I believe these resources can help us extract practical requirements based
> on real implementations and developer experiences if the group sees this is
> something that should be worked on further (also please point out if this is
> already being actively addressed by some other WG).
>
> -Anssi
>
> [1] <http://www.w3.org/TR/2009/WD-widgets-apis-20090423/>
> [2] <http://html5.org/tools/web-apps-tracker?from=2596&to=2597>
> [3]
> <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-December/017997.html>
> [4] <http://code.google.com/p/gears/wiki/NotificationAPI>
> [5] <http://msdn.microsoft.com/en-us/library/ms536392%28VS.85%29.aspx>
> [6] <https://bugs.webkit.org/show_bug.cgi?id=25463>
> [7] <http://trac.webkit.org/changeset/47056>
> [8] <https://bugzilla.mozilla.org/show_bug.cgi?id=293077>
> [9] <https://bugzilla.mozilla.org/show_bug.cgi?id=293412>
>
>
>

Received on Monday, 19 October 2009 22:19:48 UTC