/futures/deferreds model is
closer to what we're trying to accomplish with sticky channels than the DOM
event model is.
maybe when they're native. mybe.
And even then, we'd probably want to wait for dev tools catch up. I
understand how much of a pain they can be to debug.
On Tue, Jun 9
I think the only place sticky channels are used is for startup events
(deviceready, nativeready, pluginsready, etc). I think you could probably
change them to fire multiple times without breaking too much, but the
semantics of that seem really strange to me (fire the most recent event, or
all
On Tue, Jun 9, 2015 at 10:19 AM, Andrew Grieve agri...@chromium.org wrote:
I think the only place sticky channels are used is for startup events
(deviceready, nativeready, pluginsready, etc). I think you could probably
change them to fire multiple times without breaking too much
:
I think the only place sticky channels are used is for startup events
(deviceready, nativeready, pluginsready, etc). I think you could probably
change them to fire multiple times without breaking too much, but the
semantics of that seem really strange to me (fire the most recent event
I have been looking into unifying launchParameters across devices so that
all cordova apps can get some context of how they were launched/activated.
This includes everything from a url/protocol launch in another app, to a
touch on a notification (toast,local,push,... )
My intent was to add a
