Svelte Native - NativeScript UI

Provides support for using NativeScript UI in Svelte Native Applications

!example-app

Usage

npm install any of the following nativescript ui packages you wish to use.

Supported:

* Side Drawer (nativescript-ui-sidedrawer)
* List View (nativescript-ui-listview)
* Chart (nativescript-ui-chart)
* Calendar (nativescript-ui-calendar))
* Data Form (nativescript-ui-dataform)
* Gauge (nativescript-ui-gauge)
* AutoComplete (nativescript-ui-autocomplete)

In your project's app.ts file, add:

``

js

//import the components you are using

import RadListViewElement from "svelte-native-nativescript-ui/listview"

import RadSideDrawerElement from "svelte-native-nativescript-ui/sidedrawer"

import RadCalendarElement from "svelte-native-nativescript-ui/calendar"

import Charts from "svelte-native-nativescript-ui/chart"

import RadDataFrom from "svelte-native-nativescript-ui/dataform"

import Gauges from "svelte-native-nativescript-ui/gauge"

import AutoCompleteElement from "svelte-native-nativescript-ui/autocomplete"



//register them with svelte-native so they can be used in svelte components

RadListViewElement.register();

RadSideDrawerElement.register();

RadCalendarElement.register();

Charts.register();

RadDataFrom.register();

Gauges.register();

AutoCompleteElement.register();





Then use them in your

.svelte

 components:

html

  

    ...

    

       

        ...





Demo Project



The included demo project can be launched with:

sh

$ cd demo

$ npm install

$ tns run android





The demo contains examples for each of the supported elements that you can use as a starting poing.





Usage



The documentation for the supported controls can be obtained from the NativeScript site



  * Side Drawer (docs)

  * List View  (docs)

  * Chart (docs)

  * Calendar  (docs)

  * Data Form  (docs)

  * Gauge  (docs)

  * AutoComplete (docs)



The differences between the documentation at the nativescript site and the usage in svelte-native can be observed by looking at the examples in the demo project.



The main differences are the assigning of configuration elements to their parent's properties, and the handling of templates.



$3



Most configuration elements in the nativescript-ui components only have a single valid parent component and property that they can be assigned to. Svelte Native sets the default parent property for these configuration elements where possible.



eg

html



becomes:

html





Note that since the

axis elements are valid on either the horizontalAxis or verticalAxis properties, they still need to be specified using svelte-natives prop:

 directive.





$3



When a controls needs to render a child view multiple times (RadAutoCompleteTextView, RadListView) , Svelte Native configures the controls to use Template elements. 



For RadListView the item the template represents is given by the type, eg:

html





For Autocomplete it is given as the child of a

suggestionView

 element:

html