SDK Overview

VIVE Wave™ Component SDK will define various kind of feature to let different features vendor to easily provide their ability in VIVE Wave™ runtime enviroment. Currently, hand component SDK is already defined, other features are coming soon.

Component SDK Developer Guide

The VR DeviceService is responsible for transmitting data from the VR device to the VR application. All VR DeviceServices are managed by a VIVE Wave™ Server. Currently, VIVE Wave™ runtime support only one implementation for one kind feature per device.

VRComponentApplication

A base class is used to implement VIVE Wave™ component in VR DeviceService. You can provide your implemenation by creating a subclass and specifying the fully-qualified name of this subclass as the “android:name” attribute in your AndroidManifest.xml’s <application> tag. Register your feature derived classes inside the overrided onCreate function with addService API. Please refer to the following sample code snippet.

• in AndroidManifest.xml

<application android:name=".HandApplication">

• in source code

import com.htc.vr.component.VRComponentApplication

class HandApplication : VRComponentApplication() {

    override fun onCreate() {
        super.onCreate()
        addService(GestureSample())     // GestureSample is derived class from AbstractHandGesture
        addService(TrackerSample())     // TrackerSample is derived class from AbstractHandTracker
    }
}

Interfaces

Component SDK provide the following interfaces:

• Component_HandGesture : Interface to provide gesture state from hand of VIVE Wave™ runtime.(Next release version may change API, if change API developer need to rebuild AP and Hand DeviceService.)
• Component_HandTracker : Interface to provide tracker data from hand of VIVE Wave™ runtime.(Next release version may change API, if change API developer need to rebuild AP and Hand DeviceService.)