Hi, I think there might still be some value of having the cocoa + webview approach. looking at the amount of forks of cordova-osx, I assume that people wrote plugins that interact in one way or the other with the existing code.
electron is IMO great to build desktop applications, but if you want to create a mobile like app, I think it's too desktopy. our use case is more towards the kiosk mode, where the app needs to run fullscreen over several displays (which is not possible using the normal osx fullscreen mode) and also has support for multi-touch input (which we can nicely inject with a cdv plugin). further, our tests have shown that CEF is not so performant as osx webkit - at least at the time when we tried it a couple of months ago. I will provide a PR that makes the current cordova-osx build again with the instructions (CB-7143) and the new node.js based cli scripts. WDYT? regards, toby On Fri, Jun 12, 2015 at 1:07 AM, Toplak Daniel <[email protected]> wrote: > Yes I don't understand it wrong :-) > And my effort into the project is very low at the moment. > We will look forward into cordova-electron. > > Mit freundlichen Grüßen / Best regards > > CADENAS GmbH > Head of Mobile Development > Daniel Toplak > > -----Ursprüngliche Nachricht----- > Von: Shazron [mailto:[email protected]] > Gesendet: Freitag, 12. Juni 2015 09:55 > An: [email protected] > Betreff: Re: cordova-osx - mothball > > Not to diminish your work, but Atom Electron [1] (also based on Chromium) is > more aligned with Cordova as it includes node.js support built in (thus you > can use node modules which is a big plus), and already runs on OS X, Windows > and Linux. It has also in use by a lot of companies, thus there is a higher > probability of ongoing maintenance: > http://electron.atom.io/#built-on-electron > > In any case, whether through CEF or Atom Electron, to create native plugins > you will still need to bridge the code using C/C++ (unavoidable), the > difference would be for Atom Electron you would structure your code as a node > native module, which gives the advantage that it can be used not just as a > Cordova plugin, but as a regular node module outside of Cordova. > > > [1] http://electron.atom.io > > > > On Fri, Jun 12, 2015 at 12:13 AM, Toplak Daniel <[email protected]> wrote: > >> As I wrote a few month bevor I am developing a cordova platform based >> on the Chromium Embedded Framework (DEF) directly: >> https://github.com/hsimpson/cordova-cef >> We use this as a development and rapid prototyping platform on Windows. >> Theoretically it could be easily extended to OSX and Linux. >> It has the advantage to use native plugins to access operating system >> functionality. >> >> The version of the cordova implementation was from iOS and Android >> around the version 3.0 or 3.1. >> >> Mit freundlichen Grüßen / Best regards >> >> CADENAS GmbH >> Head of Mobile Development >> Daniel Toplak >> >> -----Ursprüngliche Nachricht----- >> Von: Kerri Shotts [mailto:[email protected]] >> Gesendet: Donnerstag, 11. Juni 2015 21:08 >> An: Shazron; [email protected] >> Betreff: Re: cordova-osx - mothball >> >> I’ll throw in my +1. Electron is awesome, and I’ve used it to wrap a >> PG project for a client where they are demoing the app to their >> potential clients because they don’t have devices to share from, and >> they don’t have the expertise for emulators (they are sales reps). >> Because I can wrap everything in a simple .exe (plus a couple menu >> items for switching app themes), it provides enough of a simulation >> that anyone who can double-click a file can use. (It’s not a perfect >> sim, of course, but good >> enough.) >> >> I’d hope that plugins that target the browser would hop on the >> electron platform as well, because there’s no reason why they >> shouldn’t work in electron. But I would also imagine that there could >> be electron-specific which would be very interesting to see. :-) >> >> So I’m going to be watching this with extreme interest. :-) >> >> >> >> >> On June 11, 2015 at 1:53:24 PM, Shazron ([email protected]) wrote: >> >> The potential maintainer for cordova-osx in this thread has decided to >> go in another direction -- the final nail in its coffin. Full speed >> ahead cordova-electron! Godspeed >> >> On Thu, Jun 11, 2015 at 10:59 AM, Steven Gill <[email protected]> >> wrote: >> >> > Thanks Nikhil, >> > >> > I will take a look at that PR as I work on this and provide feedback. >> > >> > >> > >> > On Wed, Jun 10, 2015 at 5:34 PM, Nikhil Khandelwal >> > <[email protected] >> > > >> > wrote: >> > >> > > There is a massive PR currently in the works that is looking to >> > > change >> > how >> > > platforms should expose their functionality: >> > > https://github.com/apache/cordova-android/pull/179 >> > > >> > > It leans on using node modules and 'require' as opposed to >> > > executing >> > shell >> > > scripts. Steve: As you try building these new platform which >> > > sounds >> > really >> > > exciting, consider using this new approach of defining the >> > > platform and provide feedback to that PR. >> > > >> > > Thanks, >> > > Nikhil >> > > >> > > >> > > -----Original Message----- >> > > From: Carlos Santana [mailto:[email protected]] >> > > Sent: Wednesday, June 10, 2015 5:22 PM >> > > To: [email protected] >> > > Cc: Ondrej Florian >> > > Subject: Re: cordova-osx - mothball >> > > >> > > Sweet Steve +1 >> > > On Wed, Jun 10, 2015 at 3:11 PM Steven Gill >> > > <[email protected]> >> > > wrote: >> > > >> > > > I started some preliminary work on this a couple of weekends ago. >> > > > >> > > > Lots to do still. Will eventually move it over to Apache. >> > > > >> > > > https://github.com/stevengill/cordova-electron >> > > > https://github.com/stevengill/cordova-js/tree/electron >> > > > >> > > > On Tue, May 26, 2015 at 7:53 PM, Carlos Santana >> > > > <[email protected]> >> > > > wrote: >> > > > >> > > > > I agree with Shaz Electron is a good platform and taking a lot >> > > > > of track now. >> > > > > Maybe another platform to cover that use case >> > > > > cordova-electron, but that would be something that is lower >> > > > > priority than the mobile platforms, but cool to see if someone >> > > > > in the community wants to dedicate time to >> > > > implement >> > > > > >> > > > > >> > > > > On Tue, May 5, 2015 at 11:19 AM Shazron <[email protected]> wrote: >> > > > > >> > > > > > Great! This is encouraging. I'll help expedite this as much >> > > > > > as I can >> > > > for >> > > > > it >> > > > > > to catch up, I'll look at any PRs and review and merge. >> > > > > > >> > > > > > On Tuesday, May 5, 2015, Ondrej Florian <[email protected]> >> > wrote: >> > > > > > >> > > > > > > If there is any interest, I would volunteer to pick it up. >> > > > > > > >> > > > > > > The Cordova-osx has its uses (I use it myself). >> > > > > > > >> > > > > > > One advantage over the Atom Electron is the plugins. >> > > > > > > Many non-UI iOS plugins will works with it out of the box. >> > > > > > > >> > > > > > > Another is that it's just another Cordova platform so you >> > > > > > > don't have >> > > > to >> > > > > > > work with yet another API. >> > > > > > > >> > > > > > > However, I think you'll rarely be satisfied with 'pure' >> > > > > > > cordova-osx (entire UI done in HTML5/js) - it's way too >> limiting. >> > > > > > > But for a hybrid app where you can mix in the native UI - >> > > > > > > it works >> > > > > well. >> > > > > > > >> > > > > > > >> > > > > > > Ondrej >> > > > > > > >> > > > > > > On 05/05/2015 01:56, "Shazron" <[email protected] >> > > > > > > <javascript:;>> >> > > > > wrote: >> > > > > > > >> > > > > > > >There is non-trivial work to create a bridge for plugins >> > > > > > > >to work >> > > > with >> > > > > > > >Electron, but it definitely has more of a future than >> > cordova-osx. >> > > > > > > > >> > > > > > > >On Mon, May 4, 2015 at 4:48 PM, Shazron >> > > > > > > ><[email protected] >> > > > > > <javascript:;>> >> > > > > > > wrote: >> > > > > > > >> A platform based off Atom Electron is more viable than >> > > > > > > >> cordova-osx >> > > > > at >> > > > > > > >> this point: http://electron.atom.io >> > > > > > > >> >> > > > > > > >> On Mon, May 4, 2015 at 4:47 PM, Shazron >> > > > > > > >> <[email protected] >> > > > > > > <javascript:;>> wrote: >> > > > > > > >>> https://issues.apache.org/jira/browse/CB-7143 >> > > > > > > >>> >> > > > > > > >>> Currently there are no resources to work on this, >> > > > > > > >>> effectively it >> > > > is >> > > > > > > >>> abandoned. Not sure what we do with this platform to >> > > > > > > >>> signal this abandonment except for docs. >> > > > > > > >>> >> > > > > > > >>> If anyone disagrees with mothballing this, chime in. >> > > > > > > > >> > > > > > > >> > > > >--------------------------------------------------------------- >> > > > >-- >> > > > >---- >> > > > > > > >To unsubscribe, e-mail: >> > > > > > > >[email protected] >> > > > > > <javascript:;> >> > > > > > > >For additional commands, e-mail: >> > > > > > > >[email protected] >> > > > > > > <javascript:;> >> > > > > > > > >> > > > > > > >> > > > > > > >> > > > > > >> > > > > >> > > > >> > > >> > > ------------------------------------------------------------------ >> > > -- >> > > - To unsubscribe, e-mail: [email protected] >> > > For additional commands, e-mail: [email protected] >> > > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
