Skip to end of metadata
Go to start of metadata

This document provides information on Android Hyperloop requirements, classes, instantiation, methods and fields, casting, interfaces, creating your own classes, and using 3rd party libraries.

Requirements

Software

See Hyperloop Requirements for software requirements for using Hyperloop with Android.

Configure tiapp.xml

Make sure to add the Hyperloop module to the <modules> section of the tiapp.xml:

Classes

Classes in Hyperloop map to the underlying classes defined in Java. For example, if you have a class such as android.view.View defined, you would reference it using a standard require such as:

This will return the View class object (it’s not an instance of a View, but the View class itself).

Once you have the Class reference returned from require, you can call normal JavaScript property and functions against it. Remember, at this point calling functions or properties against the class object above will be accessing Class level (static) Java methods (not instance level).

For example, you could get the generated view id of the View using the example:

This is because generateViewId is defined as a static method.

Instantiation

Please refer to our hyperloop-examples app in those code-level examples. For example, to use a View, the activity needs to be set:

See animateview.js (Github) for an working sample.

Methods and fields

Methods in Java are mapped to JavaScript functions. Fields in Java are mapped to JavaScript property accessors. Static methods or fields (such as constants) will be attached to the class type. For example:

Would map to the following in JavaScript:

Method resolution

If a class has overloads for a method (multiple forms of the method with different signatures, but the same name), Hyperloop will attempt to match the correct method to invoke on the Java side by matching the passed in arguments to the closest match. Typically, this involves matching the name, number of arguments and the ability to convert the passed in arguments (in-order) to the method’s parameter types. Hyperloop is slightly more liberal in accepting numeric primitives than typical method resolution due to the conversion of JavaScript Numbers.

Casting

Sometimes, interfaces define generic return types such as Object and you will need to cast them to a different type to then reference methods and properties of the class. You can pass along the object you want to wrap to the constructor of the type you want to wrap it in. For example, suppose the result of the function returned an Object but you know the implementation is actually a View. You could use the following:

Be careful with casting: If you cast an object which is actually something different, you will experience an error and likely a crash.

You can also cast a Titanium UI Component into its equivalent. For example:

Interfaces

Interfaces may be implemented using a Javascript syntax similar to an anonymous Java class. Call the constructor of the interface type with a JavaScript object that contains properties that match the interface method names, and corresponding values as function that implement them. For example, to create an instance that implements android.view.View.OnTouchListener:

Creating your own classes

Hyperloop provides you the ability to dynamically create your own Java classes at runtime. Once created, these classes can be used as normal in either Hyperloop or passed to native calls. Hyperloop generates the custom subclass using the "extend" function of the type we want to extend, which takes a single JavaScript Object as an argument containing the overriding method implementations (same as we did for interface implementations). The returned value is a new class type that subclasses the extended type. We can then use the constructor to generate instances of that subclass.

Let's create a simple custom subclass of android.view.View, and instantiate an instance of it:

 

This will create a new class in the Java runtime which will extend  android.view.View  which is equivalent to the following code (though please note that we do not generate Java source, but instead generate Dalvik bytecode that gets loaded into the runtime as a class):

 

Accessing native XML Layouts

In native Android development, you have many situations where you are inflating native XML layouts in your source-code. In Hyperloop, you can do the same with just a few lines of code:

Learn more about a native XML layouts in our Native Layout Example as part of the Hyperloop Examples app.

Using Third-party libraries

 Manual dependencies

You can use Third-party libraries in Hyperloop such as JARs and AARs.

Place the JAR and AAR files into the platform/android (Classic) or app/platform/android (Alloy) folder of your app. Hyperloop will pick up the JAR files and will generate necessary bindings. For JARs, they will be included in your app. For AAR files, they will extract resources, extract and use the class.jar, *.so file, and so on.

Gradle Dependencies

Instead of placing your Android archives into your project manually, you can also use Gradle to pull down any library and its dependencies. Here is a quick example of using the Mapbox Android SDK via Gradle:

build.gradle

In the above Gradle file, the Mapbox Android SDK is downloaded to platform/android (Classic) and can be changed to app/platform/android if used in Alloy. You can see a full example of using Gradle, CocoaPods (iOS) and modern ES6+ in the Ti.Mapbox module.

Third-party Examples

Make sure to check out more Android third-party libraries (like Localytics, SSDP, Shimmer) in our Hyperloop Sample App.