Rayneo X2 Android SDK
输入“/”快速插入
Rayneo X2 Android SDK
1.
Overview
Main purpose of this document: introduce how to develop an APP on the RayNeo X2 AR glasses based on the native Android development method. What are the limitations and differences compared with mobile phone development, and how to solve these problems by connecting to the SDK we provide.
2.
Background Introduction
RayNeo X2 is an AR glasses which contains a complete Android system (Android 12). Compared with general mobile app development, there are the following differences:
•
Screen: Generally, there is only one screen on the mobile phone, while there are two screens on the glasses. The screen on the left is projected to the left eye, and the screen on the right is projected to the right eye. What we receive from the system is a logical screen combining both left and right screens. When the general mobile phone app runs on the glasses, the screen may seem separate and abnormal, i.e. the left screen displays the left side, and the right screen displays the right side, which will result in the overlap of the left and right parts. Therefore, when designing the layout, we suggest developers place the same UI on both sides to solve the overlapping problem. Rayneo X2 Android SDK (also named 'MercuryAndroidSDK') provides many basic components (View, Activity, Dialog, Toast, etc.) to solve the overlapping problem so that developers can quickly start developing without writing a lot of template code.
•
Event response and focus switching: The touch event on the mobile phone screen is two-dimensional, including X and Y coordinates. But on the glasses, there is only one-dimensional touch on the temple, i.e. the dynamically changeable X coordinate, while the Y coordinate is a fixed value. To control the two-dimensional UI page with one-dimensional touch, you need to import a focus mechanism. Only when the control acquires the focus can it respond to the touch event. The SDK provides basic focus-switching logic and touch event response processing mechanism.
Rayneo X2 Android SDK mainly solves the challenges caused by the above two situations. However, if you can solve the above problems alternatively, you can completely abandon the SDK and encapsulate your own framework. You are welcome to share your solution with us.
3.
Quick Access to SDK
3.1
Open ViewBinding
The Rayneo X2 Android SDK is encapsulated based on ViewBinding. Therefore, please open the viewbinding configuration in build.gradle
buildFeatures {
viewBinding = true
}
3.2
Configure mata-data
<application
android:name=".MyApplication"
....
>
<meta-data android:name="com.rayneo.mercury.app" android:value="true" />
</application>
In the application tag of the main module 'AndroidManifest file', add the above meta-data tag. When its value is true, it can be recognized by the system to start your application from the default startup entry.
3.3
Introduce dependencies
3.3.1
TCL Innovations' Private Maven Access
If you have access to TCL Innovations' private Maven service, you can include a private maven server in settings.gradle
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
google()
mavenCentral()
// 配置雷鸟私有Maven服务器
maven {
url 'http://172.16.46.52:9998/repository/maven-public/'
allowInsecureProtocol = true
}
}
}
Introduce the following dependencies in the build.gradle of the main module of the project to complete the dependency addition:
implementation 'com.ffalcon.mercury:MercuryAndroidSDK:0.1.0'
3.3.2
AAR file access