C

Qt IVI Generator Extensions

Qt IVI Generator Extensions allows building a middleware layer for accessing Android Automotive Vehicle Properties. It makes use of tools and core APIs provided by the Qt IVI module. It also delivers additional Qt IVI Formats that can be used to generate additional project types:

Project Type	Description
server_android_carapi_qtro	Generates a QtRemoteObjects based back end server implementation for the API first generated by the front end option. This server delivers both complete and stub implementation required to access Android Automotive Vehicle Properties with use of QtRemoteObjects Back end
backend_android_carapi_jni	Generates JNI based back end for the API first generated by the front end option. This back end delivers both complete and stub implementation required to access Android Automotive Vehicle Properties.

YAML Annotations

In order to be able to access Android Automotive Vehicle Properties, additional configuration has to be provided next to the QFace IDL itself. In the Qt IVI Generator Extensions the following annotations (in the accompanying YAML file) are used for Interface Object type:

The imports tag:
```
config_android_automotive:
    imports: ["android.car.VehicleAreaSeat","android.car.VehicleAreaWindow"]
```
Defines a list of Android API imports that contain defines/consts related to properties handled by this interface (e.g. zone id consts). The entries will be converted into the list of imports:
```
import android.car.VehicleAreaSeat;
import android.car.VehicleAreaWindow;
```

The zoneAliases tag:

config_android_automotive:
    zoneAliases: ["DRIVER_ZONE_ID = VehicleAreaSeat.SEAT_ROW_1_LEFT | VehicleAreaSeat.SEAT_ROW_2_LEFT | VehicleAreaSeat.SEAT_ROW_2_CENTER",
                  "PASSENGER_ZONE_ID = VehicleAreaSeat.SEAT_ROW_1_RIGHT | VehicleAreaSeat.SEAT_ROW_2_RIGHT",
                  "SEAT_ALL = DRIVER_ZONE_ID | PASSENGER_ZONE_ID"]

Defines zones aliases for individual properties e.g. to be used with zones that group multiple sub-zones. The entries will be converted into the list of Java constants:

public static final int DRIVER_ZONE_ID = VehicleAreaSeat.SEAT_ROW_1_LEFT | VehicleAreaSeat.SEAT_ROW_2_LEFT | VehicleAreaSeat.SEAT_ROW_2_CENTER;
public static final int PASSENGER_ZONE_ID = VehicleAreaSeat.SEAT_ROW_1_RIGHT | VehicleAreaSeat.SEAT_ROW_2_RIGHT;
public static final int SEAT_ALL = DRIVER_ZONE_ID | PASSENGER_ZONE_ID;

The zoneMappings tag:

config_android_automotive:
    zoneMappings: {"" : "SEAT_ALL",
                   "Driver": "DRIVER_ZONE_ID",
                   "Passenger" : "PASSENGER_ZONE_ID"}

Defines the zone mapping from QtIVI's QML string representation to the underlying Java enum zone for Android Automotive. This will initialize a C++ map as follows:

m_zoneMappings.insert(QStringLiteral(""), QAndroidJniObject::getStaticField<jint>(
                                                                    "io/qt/qtivi/android/vehiclefunctions/QIviClimateControlSensors",
                                                                    "SEAT_ALL"));
m_zoneMappings.insert(QStringLiteral("Driver"), QAndroidJniObject::getStaticField<jint>(
                                                                    "io/qt/qtivi/android/vehiclefunctions/QIviClimateControlSensors",
                                                                    "DRIVER_ZONE_ID"));
m_zoneMappings.insert(QStringLiteral("Passenger"), QAndroidJniObject::getStaticField<jint>(
                                                                    "io/qt/qtivi/android/vehiclefunctions/QIviClimateControlSensors",
                                                                    "PASSENGER_ZONE_ID"));

In the Qt IVI Generator Extensions the following annotations (in the accompanying YAML file) are used for Property Object type:

The vhalId property:
```
config_android_automotive:
    vhalId: "HVAC_AC_ON"
```
Defines the related android property id, as defined in Android Automotive Vehicle Properties.
The zone property:
```
config_android_automotive:
    zone: ["DRIVER_ZONE_ID", "PASSENGER_ZONE_ID"]
```
Defines the zone enum(s) for the related android property. The zone can be either one or more of the values defined under the interface's zoneAliases. If a zone holds multiple values, these values have to be defined as an array. The QML component can then decide which zone to control. For example:
```
ClimateControl {
    id: climateControl
    zone: "Driver"
}
```
To get the value of climateControl for a given zone in QML, use the following snippet:
```
property int tempValue = climateControl.zoneAt.Driver.targetTemperatureSet
```
The vhalType property:
```
config_android_automotive:
    vhalType: "BOOLEAN"
```
A vehicle property type as defined in Vehicle properties.
The javaType property:
```
config_android_automotive:
    javaType: "Boolean"
```
The vehicle property Java type.

Structure for Generated Projects

In the generator output directory, first, a new subfolder is created and named after the module ID. All the generated files are placed in this folder. The tables below describe the files that are generated for the project types delivered by the Qt IVI Generator Extensions.

Qt Remote Objects Server

This generator template shall be used together with a project that contains the Qt Services code. The server_android_carapi_qtro template is only available if qmake finds the QtRemoteObjects module. The code produced contains:

the code for establishing the connection
the code that enables the JNI interface to call the Java back end logic
default implementation of complete Java back end logic required to access Android Automotive Vehicle Properties
Java interface that can be implemented to provide back end logic, if default implementation doesn't meet the requirements

Filename	Purpose
core.h/cpp	Code for establishing the connection and starting the remoting for the source objects.
.pri	A standard Qt `.pri` file that contains all the generated files. Use this `.pri` file to include the generated files into a qmake project. Also includes the `.rep` file to the project and calls the remote object compiler.
.rep	The input file for the Qt replica compiler to produce the source class code.
backend.h/cpp	Source QtRemoteObject implementation (that serves as adapter for Java back end implementation).
native_mappings.cpp	JNI bindings between {{interface\|lower}}backend.cpp and Java back end implementation. There is only one instance of this file that provides mapping for all interfaces defined in the module.
android/src/io/qt/{{module\|qml_type\|replace('.', '/')\|lower}}/{{interface}}.java	Provides an interface to notify {{interface\|lower}}backend.cpp on property value change.
android/src/io/qt/{{module\|qml_type\|replace('.', '/')\|lower}}/I{{interface}}.java	Java interface that needs to be implemented by the QtService sub-class in order to provide custom back end logic if default implementation doesn't meet the requirements
android/src/io/qt/{{module\|qml_type\|replace('.', '/')\|lower}}/{{interface}}Sensors.java	Provides wrappers around Android Automotive Vehicle Properties that are used by default Java back end implementation.
android/src/io/qt/{{module\|qml_type\|replace('.', '/')\|lower}}/{{interface}}Backend.java	Default Java back end implementation.

The following diagram presents the possible use case scenarios:

using custom implementation for accessing vehicle property
using default implementation for accessing vehicle properties

JNI Back End

This generator template shall be used on a plugin project. The backend_android_carapi_jni template provides the production back end that can be used to access Android Automotive Vehicle Properties. The code produced contains:

the code for setting back end plugin
the code that enables JNI interface to actual Java back end logic
default implementation of complete Java back end logic required to access Android Automotive Vehicle Properties
Java interface that can be implemented to provide back end logic if default implementation doesn't meet the requirements

Filename	Purpose
plugin.h/cpp	Files defining implementation of QtIvi back end plugin implementing QIviServiceInterface.
.json	File containing identifiers of the exposed feature interfaces needed by the Qt plugin system.
.pri	A standard Qt `.pri` file that contains all the generated files. Use this `.pri` file to include the generated files into a qmake project.
backend.h/cpp	QIviZonedFeatureInterface/QIviFeatureInterface implementation (that serves as adapter for Java back end implementation).
native_mappings.cpp	JNI bindings between {{interface\|lower}}backend.cpp and Java back end implementation. There is only one instance of this file that provides mapping for all interfaces defined in the module.
android/src/io/qt/{{module\|qml_type\|replace('.', '/')\|lower}}/{{interface}}.java	Provides an interface to notify {{interface\|lower}}backend.cpp on property value change.
android/src/io/qt/{{module\|qml_type\|replace('.', '/')\|lower}}/I{{interface}}.java	Java interface that needs to be implemented by QtActivity sub-class in order to provide custom back end logic if default implementation doesn't meet the requirements
android/src/io/qt/{{module\|qml_type\|replace('.', '/')\|lower}}/{{interface}}Sensors.java	Provides wrappers around Android Automotive Vehicle Properties that are used by default Java back end implementation.
android/src/io/qt/{{module\|qml_type\|replace('.', '/')\|lower}}/{{interface}}Backend.java	Default Java back end implementation.

The following diagram presents the possible use case scenarios:

using default implementation for accessing vehicle properties
using custom implementation for accessing vehicle property

Available under certain Qt licenses.
Find out more.