The first task is done by the NativeScript CLI by adding the source files to the generated _.xcodeproj_. For the second one the Metadata Generator needs to find a [module.modulemap](https://clang.llvm.org/docs/Modules.html) of the compiled modules.

In order to satisfy the above constraints the developer has to:

**1)** Place the source files in _App_Resources/iOS/src/_

**2)** Create a modulemap for the Objective-C files

For a detailed walkthrough on how to use native iOS source code in NativeScript [here](https://www.nativescript.org/blog/adding-objective-c-code-to-a-nativescript-app).

myObject.myMethod(10) // myMethod(int) will be called.

- Implicit **floating-point** conversion:

myObject.myMethod(10.5) // myMethod(double) will be called.

- Explicitly call an overload: <br/>

To enable developers call a specific method overload, the Runtime exposes the following functions directly in the global context:

* byte(number) → Java primitive byte

* short(number) → Java primitive short

* float(number) → Java primitive float

* long(number) → Java primitive long (in case the number literal fits JavaScript 2^53 limit)

* long("number") → Java primitive long (in case the number literal doesn't fit JavaScript 2^53 limit)

myObject.myMethod(long('123456')) // will convert "123456" to Java long and will call myMethod(long)

myObject.myMethod(10) // myMethod(Int) will be called.

- Implicit **floating-point** conversion:

myObject.myMethod(10.5) // myMethod(Double) will be called.

- Explicitly call an overload: <br/>

To enable developers call a specific method overload, the Runtime exposes the following functions directly in the global context:

myObject.myMethod(long('123456')) // will convert "123456" to Kotlin Long and will call myMethod(Long)

var singleFile = files[0] // the indexed getter callback is triggered and a proxy object over the java.io.File is returned

}


main-view-model.js

One of NativeScript's strongest capabilities is the access to Android (also referred to as **'Java/Kotlin'** or **'native'**) APIs inside JavaScript/TypeScript. That's possible thanks to build-time generated [Metadata](./overview.md) chunks which hold the information about the public classes from the Android SDK, Android support libraries, and any other Android libraries which may be imported into your Android NativeScript project.

For example, if you need to work with the Google API for Google Maps, after following the installation guide, you may need to access packages from the plugin like `com.google.android.gms.maps`, which you can find a reference for at [Google APIs for Android Reference](https://developers.google.com/android/reference/com/google/android/gms/maps/package-summary)

- `isPassThroughParentEnabled` - Gets or sets a value indicating whether touch events should pass through to a parent view of the layout container in case an interactive child view did not handle the event. Does not affect the appearance of the view. The default value is `false`.

Playground application demonstrating the usage of the three properties can be found [here](https://play.nativescript.org/?template=play-tsc&id=6c9GA0).

});

)

In the `getFile` method we could also specify the path, where the file to be saved. This scenario is demonstrated in the example below, where the image file will be kept in the current application folder.

As an additional feature for Android, NativeScript supports `decodeWidth` and `decodeHeight`. These properties will **downsample** your image so that it will take less memory. The goal is to avoid as much as possible out of memory exceptions caused by images being loaded into memory and at the same time display crispy images.

When working with the decode properties, the following considerations should be taken:

- Image caching now takes into account the `decodeWidth` and `decodeHeight` values. Identical images with different decode property values will now be retrieved and saved separately in the cache. This results in better quality images. If you have a small version of the image in a master list and want to decode it with 100 x 100 DP, and then want to display it in 1000 x 1000 DP on the detail page, the detailed image will now not be blurry. This also means you can now control caching - using the same image with the same decode parameter values will still get the image from the cache.

</StackLayout>

The `Image` module will use internal memory and disk cache, so when loaded the module stores the images in the memory cache, and when they are not needed anymore, the `Image` module saves the images in the disk cache. This way the next time the application needs the same image NativeScript will load it from memory or the disk cache. Setting property `useCache` to `false` could be used to bypass image cache and load the image as it is on the first request to the specified URL.

**API Reference for** [Image Module](/api-reference/modules/_ui_image_.html)

The above commands will start a server listening on port 8080. Remember to update the URL in your app to match the address/port where the server is running.