On Wed, Oct 17, 2012 at 1:59 PM, Andrew Grieve wrote:
> I think probably the best thing to do is to just always return false for
> webkitNotifications.checkPermission() on iOS when the app is in the
> foreground.
I assumed permissions is checked only once, so I don't think the value
returned here
I think probably the best thing to do is to just always return false for
webkitNotifications.checkPermission() on iOS when the app is in the
foreground.
Any custom UI we attempt will likely not appease developers. Let them
implement their own in-app notification area if that's what they want.
If
Toasts are delicious but what would the iOS analog be? (Guess we could
write a toasty impl for iOS which would be a cool feature.)
On Wed, Oct 17, 2012 at 7:36 AM, Michal Mocny wrote:
> Do we want to ignore notifications when app is in foreground (call
> onerror), or use a different mechanism, li
Do we want to ignore notifications when app is in foreground (call
onerror), or use a different mechanism, like a custom growl/toast, or
something?
Either way, since the w3c spec does not specify how to delay local
notifications or use push, there is nothing useful it can do on ios as
is. I'll wr
I can.. ? Not sure what your point is.
On 10/16/12 5:56 PM, "Jesse" wrote:
>You can't ring your doorbell from inside the house either ...
>
>On Tue, Oct 16, 2012 at 5:50 PM, Filip Maj wrote:
>>
- StatusBar Notifications: Intended for background services to
notify a
user to s
You can't ring your doorbell from inside the house either ...
On Tue, Oct 16, 2012 at 5:50 PM, Filip Maj wrote:
>
>>>- StatusBar Notifications: Intended for background services to
>>>notify a
>>>user to start some action (instead of just doing the action without
>>>users'
>>>explicit
>>- StatusBar Notifications: Intended for background services to
>>notify a
>>user to start some action (instead of just doing the action without
>>users'
>>explicit intent) -- so what does this mean for iOS without background
>>services?
>
>I *think* a fallback to local notificati
* agree that status bar and local notifications should, in the fullness of
time, be core plugins
* push notifications are a little trickier, because apps that use wildcard
provisioning profiles can't use push notifications. I'm not sure if just
having the push code in there would cause compilation/
Hey Michal,
Working on notifications would be awesome. One thing I'd like to point out.
We have a spreadsheet to help track the state of all plugins across all the
platforms. This may contain info that is helpful:
https://docs.google.com/spreadsheet/ccc?key=0Al813Y70ZNWbdC0zRFduOEY2M0tjZWYxOVVUbm
On Fri, Oct 12, 2012 at 12:01 PM, Brian LeRoux wrote:
> Dude, this post wins for best title but also a big THANK YOU for doing
all this legwork. I moved into the wiki to help collab/tracking here
> http://wiki.apache.org/cordova/Core%20API%20Audit
>
> Goals are perfectly in line w/ what I'd say
Dude, this post wins for best title but also a big THANK YOU for doing
all this legwork. I moved into the wiki to help collab/tracking here
http://wiki.apache.org/cordova/Core%20API%20Audit
Goals are perfectly in line w/ what I'd say is "The Cordova Way".
(Irony quotes somewhat intentional.)
A qu
Hi All!
Notifications seem to be an important and popular feature, but the plugins
we have in the phonegap-plugin repo are a bit of a mess. I was hoping to
take a stab at fixing that.
I figured I'de start by figuring out where we are at today, and open up
discussions for where we want to be.
(W
12 matches
Mail list logo
