Repository navigation
Support for desktop OSs (OSX, Windows, Linux) #27
Description
Activity
How do I up-vote this?
+1 - Core dev team might want to take a look at the latest version of WinJS library for ideas.
This'd be pretty cool. And with windows 10 Chakra integration that'd be not too hard, I'd imagine. Maybe it'd also be a step for integrating with windows phone, too.
+1
Reacted by Yeikel Santana, icode and Alexander MillsReacted by Karol Mierzejewski, Brian Webb, Rafael Belvederese, Richard King, Whit Huntley, Tobias Kern, Lucia Scarlet, Nick, Cristián Pérez, Lesego Mabe and 4 moreCan somebody talk about the feasibility of doing this. It looks pretty doable based on the iOS runtime as there is a pretty clean layer for calling Objc-C.
Yes it is doable and relatively easy (in a matter of week) a POC app can be created that can show a running MacOS app written in {N} and accessing the native desktop APIs. The real effort will after that when the abstraction layer that will allow you to reuse the UI declarations between mobile and desktop should be written.
I wonder if some of you is interested in doing this POC or dealing with the abstraction layer? It is really not a top priority for the moment and I don't see it becoming a priority in the next 6 months for the core team.
I wish you keep mobile separated from desktop development. Please, keep the core lite. This can be somekind of optional plugin, dont you think?
Reacted by Arianit+1
Reacted by Karol Mierzejewski, Brian Webb, Rafael Belvederese, Ivan Kara, Tobias Kern, Lucia Scarlet, 0x1A4, Cristián Pérez, shreyasm-dev, Caesar Schinas and 1 moreIf desktop support is a lower priority than mobile, maybe it could be implemented on top of Qt?
Since they've already done the work of wrapping up a JS runtime and cross-platform UI abstraction together, it seems like NativeScript could hypothetically just map its own UI markup's primitives to the equivalent QML code.
Reacted by Paul, Arianit and Martin BraunReacted by Caesar Schinas+1
Reacted by Karol Mierzejewski, Brian Webb, Rafael Belvederese, Dmitry Demin, Ivan Kara, Tobias Kern, Lucia Scarlet, Javier Alfonso, 0x1A4, Cristián Pérez and 4 moreI don't think QT is needed. Ubuntu already supports QML natively for it's UI markup. And also JavaScript and Swift for it's controller logic.
So only Swift (plus some QML) is necessary to support iOS, OSX, and Ubuntu. But, as mentioned above, the hard part is the API differences.
HOWEVER, with interoperability being an official goal of Swift 3.0, the syntactic differences between Apple APIs (Foundation, AppKit, UIKit, etc) might be lessened. Which should make the {N} abstraction layer easier to create for all 3 platforms.
So perhaps Swift 3.0 is a good runtime target for this goal (even if it temporarily excludes Windows).
+1
Reacted by Jan Böhler and icodeReacted by codec-abc, Brian Webb, Rafael Belvederese, Dmitry Demin, Ivan Kara, Tobias Kern, Javier Alfonso, Cristián Pérez, shreyasm-dev, Caesar Schinas and 1 moreno Swift. Why adding a dependency on a language not absolutely needed for the desktop, in the sense of Java being needed for Android.
Reacted by ArianitAre there any plans to support desktop OS in the near future? Maybe macOS?
Reacted by Sage Arbor, Mike, Todd Gao, Tarun Elankath, Brian Webb, icode, yellow, Lukas Bombach, tfpdeveloper, Cryptochats and 6 more23 remaining items
I think this project worth to look at.
https://github.com/tauri-apps/tauriReacted by Pavitra Golchhais the only way NativeScript can win the popularity contest '__')
Import to remember that search trends ≠ actual industry adoption. Nevertheless, desktop support would be great!
Reacted by shreyasm-dev and ArianitThis feature right now is not no optional ... it is almost required to be competitive with other implementations like Flutter, Blazor Mobile Bindings (allow not only use platform API but also use hybrid approach and mix code) and so on
Reacted by ArianitI brought up a similar idea in an earlier comment on this issue five years ago, but would it make sense for NativeScript to target Flutter rather than each platform directly (or as a third "platform" in addition to Android and iOS)? Since Flutter supports desktop platforms, and version 2 released today now has production-quality support for the web, this would kill four birds with one stone.
Alternatively, what about just adding web support and putting a pin in native desktop support? While not ideal, Electron is basically fine on desktop, and being able to target every platform with one code base would be a huge improvement from the current situation where we need to maintain different templates for web and native.
Reacted by Jamie Birch, ૮༼⚆︿⚆༽つ and Luke HardimanMakes sense! The blog post said production-quality, but upon testing the flutterfolio.com demo, while it looked great at first glance (and is certainly impressive regardless), it spiked my CPU to 50+% just by being open in the foreground and had enough subtle issues that I wouldn't consider using it production in its current form.
And awesome, glad to hear that! I'll go ahead and follow the RFC issue to keep up with the progress.
Reacted by Nathanael Anderson, ૮༼⚆︿⚆༽つ and Lukas Hahn+1
Reacted by ૮༼⚆︿⚆༽つ, Dušan Gvozdenović, Lukas Hahn and Daniel HerrCould I get some help adding NativeScript-vue into this Desktop + Web boilerplate? It's set to build for both:
There are branches for Vue 2 and Vue 3.
Reacted by ૮༼⚆︿⚆༽つI have interest for GNU/Linux support
May top post be edited since URL is gone:
Relate-to: NativeScript/rfcs#11
I would love to see this happening and I think it should head in the direction of UWP on Windows and Mac Catalyst on macOS. The former will be the most work, the latter should be possible easily.
Until this is done, we really have to leverage PWA or things like Electron. True native is different.
Reacted by Philippe Coval and ChrisChou@listepo I got something working
- core feat: windows #11272
- cli feat: windows nativescript-cli#6065
- templates feat: windows nativescript-app-templates#244
you can try this sample app https://github.com/triniwiz/nativescript-windows-pokedex
This would be a killer feature. If you even made a layer for NW.js, that would be awesome.
Please vote for this issue in our ideas portal.
Please don't write a comment saying
+1. Instead vote for it in the ideas portal or by hitting the quick reply buttons just below this post.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.