Content deleted Content added
No edit summary |
Duplicating Structure section |
||
Line 23:
Platform independent user interfaces are defined using [[XML]] files. NativeScript then uses the abstractions described in the XML files to call native elements of each platform. Application logic developed in Angular2 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>http://www.heise.de/developer/artikel/Mit-JavaScript-wie-hausgemacht-NativeScript-3282619.html</ref>. Telerik aims for a ratio of 90% common code between the iOS and Android platforms <ref>http://www.telerik.com/platform/nativescript/faq</ref>.
▲=== Direct access to native platform APIs and Controls ===
Platform independent user interfaces are defined using [[XML]] files<ref>https://docs.nativescript.org/ui/basics</ref>. NativeScript uses the XML data structures representing the cross platform abstraction to trigger platform specific code that directly interacts with the native elements of the deploy target operating system. This means a call to a NativeScript provides UI abstraction for Button, will directly call UIButton on iOS <ref>https://github.com/NativeScript/NativeScript/blob/master/tns-core-modules/ui/button/button.ios.ts</ref> or com.android.widget.Button on Android <ref>https://github.com/NativeScript/NativeScript/blob/master/tns-core-modules/ui/button/button.android.ts</ref>. Application logic developed in Angular2 and TypeScript can be developed independent of the target platform as well. A NativeScript app is build using the node.js runtime and tooling <ref name=heisede3282619/>. Telerik aims for a ratio of 90% common code between the platforms <ref>http://www.telerik.com/platform/nativescript/faq</ref>
| |||