NativeScript: Difference between revisions

Revision as of 21:43, 6 November 2024

Revision as of 04:21, 7 November 2024

Line 23:

==Structure==

NativeScript and all the required plugins are installed using the package manager [[Npm (software)|npm]]. Projects are created, configured, and compiled via the command line or a GUI tool called NativeScript Sidekick.<ref>{{Cite web|url=https://www.nativescript.org/nativescript-sidekick|title=NativeScript Sidekick - your faithful companion for app development|website=NativeScript.org|language=en|access-date=2017-10-31|archive-date=2017-11-07|archive-url=https://web.archive.org/web/20171107004639/https://www.nativescript.org/nativescript-sidekick|url-status=live}}</ref>

Platform-independent user interfaces are defined using [[XML]] files. NativeScript then uses the abstractions described in the XML files to call native UI elements of each platform. Application logic developed in Angular and TypeScript can be developed independent of the target platform as well. A NativeScript mobile application is built using the node.js runtime and tooling.<ref name=heisede3282619>{{Cite web|url=https://www.heise.de/developer/artikel/Mit-JavaScript-wie-hausgemacht-NativeScript-3282619.html|title=Mit JavaScript wie hausgemacht: NativeScript|first=Tam|last=Hanna|website=Developer|date=9 August 2016 |access-date=2022-07-12|archive-date=2021-07-25|archive-url=https://web.archive.org/web/20210725085644/https://www.heise.de/developer/artikel/Mit-JavaScript-wie-hausgemacht-NativeScript-3282619.html|url-status=live}}</ref> Progress aims for a ratio of 90% common code between the iOS and Android platforms.<ref name="nativescript.org">{{Cite web|url=https://www.nativescript.org/|title=Frequently asked questions about NativeScript|website=NativeScript.org|access-date=2016-03-20|archive-date=2016-03-18|archive-url=https://web.archive.org/web/20160318132229/https://www.nativescript.org/|url-status=live}}</ref>

==Direct access to native platform APIs and controls==