You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Dave Johnson <da...@gmail.com> on 2012/10/24 00:47:15 UTC
Cordova desktop (again)
Hey all, I just had a discussion about cordova desktop and, while we
have discussed this at length in the past, given the new embeddable
view architecture of cordova it might make sense to revisit from the
perspective of just creating an embeddable view for osx and windows.
Other than getting some rough consensus on it and creating a couple of
tickets (maybe repos too since we are migrating all that now with the
graduation) there's not really anything specifically that we need to
do for it at the moment.
Thoughts?
-dave
Re: Cordova desktop (again)
Posted by Shazron <sh...@gmail.com>.
I've been thinking about cordova-osx and how to proceed with respect
to plugins, which all the APIs are of course implemented in.
There are two ways to approach this -- direct object binding (so the
API will be synchronous), or asynchronous through a bridge like how
iOS does it (possible plugin re-use from iOS? dunno).
Currently I have some test functions in there using direct object
binding: https://github.com/apache/incubator-cordova-mac/blob/master/CordovaMac/CordovaMac/WebViewDelegate.m#L30
sound.play
notification.alert
console.log
Direct object binding is not too bad, but specifying a new function is
a bit tedious, note the isSelectorExcludedFromWebScript and
webScriptNameForSelector functions where we need to specify the
functions to express:
https://github.com/apache/incubator-cordova-mac/blob/master/CordovaMac/CordovaMac/Commands/CDVSound.m
On Tue, Oct 23, 2012 at 3:47 PM, Dave Johnson <da...@gmail.com> wrote:
> Hey all, I just had a discussion about cordova desktop and, while we
> have discussed this at length in the past, given the new embeddable
> view architecture of cordova it might make sense to revisit from the
> perspective of just creating an embeddable view for osx and windows.
> Other than getting some rough consensus on it and creating a couple of
> tickets (maybe repos too since we are migrating all that now with the
> graduation) there's not really anything specifically that we need to
> do for it at the moment.
>
> Thoughts?
>
> -dave