Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Bryan Higgins <bhiggins@blackberry.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Subject: Re: prompt dialog for the Notification API?
Thread-Topic: prompt dialog for the Notification API?
Thread-Index: AQHOIBak2OA9jyhN5kiJ2bNrPv8xp5ikAdeA
Date: Wed, 13 Mar 2013 18:28:30 +0000
Message-ID: <6FCEDB040CA65C43AA491D9DA06AB19DC02579@XMB116CNC.rim.net>
In-Reply-To: 
 <CAEeRA4rF70PCf5Df4ozm1o2TjD9MRthxqvW1h+tHaC-6z2COdA@mail.gmail.com>
Accept-Language: en-US, en-CA
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9AC1ABFC1EAA1E4A960B457D1F49C9F4@rim.com>
content-transfer-encoding: quoted-printable
MIME-Version: 1.0

BB10 has support for this and I'll volunteer to do the implementation.

If a JIRA task has or is being created, please assign it to me (bryanhiggins=
).

Thanks,
Bryan


From: Filip Maj <fil@adobe.com<mailto:fil@adobe.com>>
Date: Wed, Mar 13, 2013 at 12:55 PM
Subject: Re: prompt dialog for the Notification API?
To: "dev@cordova.apache.org<mailto:dev@cordova.apache.org>" <dev@cordova.apa=
che.org<mailto:dev@cordova.apache.org>>


No go ahead James, no point waiting.

On 3/12/13 1:59 PM, "James Jong" <wjamesjong@gmail.com<mailto:wjamesjong@gma=
il.com>> wrote:

>Great!  Thanks for all the feedback.  I'll start working on it.
>
>Fil - on the helper scripts.  Is this something you want me to wait on
>before opening up the JIRA for this?
>
>Max - thanks for alerting me to the buttonLabels bug.
>
>-James Jong
>
>On Mar 12, 2013, at 3:32 PM, Filip Maj <fil@adobe.com<mailto:fil@adobe.com>=
> wrote:
>
>> What Michal said!
>>
>> I will sort out some helper scripts for filing issues like this soon-ish
>> and let you guys know/provide an overview (came up in the F2F)
>>
>> On 3/12/13 1:16 PM, "Michal Mocny" <mmocny@chromium.org<mailto:mmocny@chr=
omium.org>> wrote:
>>
>>> I think its generally the case that we don't want to hold back
>>>platforms
>>> just because others will not have support, so I'de say go ahead with
>>>iOS
>>> and Android without holding back.
>>>
>>> However, whenever possible be cross platform friendly and make the job
>>>of
>>> implementation elsewhere feasible.
>>>
>>> The way to do this is to file a JIRA bug for the feature, and create
>>> subtasks to implement on each platform (The major 4 are iOS, Android,
>>> Windows Phone, BlackBerry), then assign the ones you plan to do to
>>> yourself.
>>>
>>> I'm not sure where best to document platform support for api's, but as
>>> soon
>>> as the feature lands anywhere, it should be documented publicly.
>>>
>>> -Michal
>>>
>>>
>>> On Tue, Mar 12, 2013 at 11:55 AM, Becky Gibson
>>> <gibson.becky@gmail.com<mailto:gibson.becky@gmail.com>>wrote:
>>>
>>>> +1
>>>>
>>>> I think it would be worthwhile to add this.  We just need confirmation
>>>> from
>>>> the other platforms that this feature is available.
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Mar 11, 2013 at 5:04 PM, James Jong <wjamesjong@gmail.com<mailt=
o:wjamesjong@gmail.com>>
>>>> wrote:
>>>>
>>>>> I was looking at the Notification API and noticed that we have
>>>> existing
>>>>> support for alert and confirm dialogs but do not have one for prompt.
>>>> I
>>>>> think it would good to add this missing function to the Notification
>>>> API.
>>>>> It seems a natural fit alongside the alert and confirm methods.
>>>>>
>>>>> To mirror the current dialogs in the Notification API, the js method
>>>> would
>>>>> look something like:
>>>>> navigator.notification.prompt(message, promptCallback, [title],
>>>>> [buttonLabels])
>>>>> message: Dialog message to display (String)
>>>>> promptCallback: Callback to invoke with index of button pressed (1 or
>>>> 2).
>>>>> (Function)
>>>>> title: Dialog title (String) (Optional, Default: "Prompt")
>>>>> buttonLabels: Comma separated string with button labels (String)
>>>>> (Optional, Default: "OK,Cancel")
>>>>>
>>>>> The goal would be to have this across all our supported platforms.  I
>>>>> would like to create a JIRA item and have sub-tasks for each
>>>> platform.  I
>>>>> plan on contributing the code for iOS and Android.  I also will
>>>>>update
>>>>> mobile-spec tests and write the API documentation.
>>>>>
>>>>> My questions are:
>>>>> (1) Is this a reasonable addition to the Notification API?
>>>>> (2a) If so, can we initially have support for a few platforms and add
>>>> more
>>>>> as we go along?
>>>>> (2b) Can we go ahead and publicly document the API or wait until we
>>>> have
>>>>> support across the platforms?
>>>>>
>>>>> If we agree this is good to have, here's the summary of tasks I plan
>>>> to
>>>>> proceed with:
>>>>> create a JIRA issue with sub-tasks for each platform
>>>>> contribute the code for iOS and Android
>>>>> add prompt tests to mobile-spec
>>>>> create the prompt API documentation
>>>>>
>>>>> Thoughts or comments?
>>>>>
>>>>> -James Jong
>>>>
>>
>


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.