This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
android:agtek_lib_location_manager_architecture [2014/08/02 22:47] mjallison [Leica ICG60 Structure] |
android:agtek_lib_location_manager_architecture [2019/10/21 16:00] (current) timm |
||
---|---|---|---|
Line 18: | Line 18: | ||
===== Extending the framework ===== | ===== Extending the framework ===== | ||
- | Adding new devices is relatively straight forward. For each new device you must write a new class to be the LocationDevice and write a new class to be the LocationProvider. It is up to the Device to perform detection and verification of the ohysical device, while the Provider is to provide the normalized location updates when they are made available via the physical device. | + | Adding new devices is relatively straight forward. For each new device you must write a new class to be the LocationDevice and write a new class to be the LocationProvider. It is up to the Device to perform detection and verification of the physical device, while the Provider is to provide the normalized location updates when they are made available via the physical device. |
If the instrument being added is a Bluetooth device, the you should extend com.agtek.location.bluetooth.AbstractBluetoothDevice instead of the normal LocationDevice and the Provider should extend com.agtek.location.bluetooth.AbstractBluetoothProvider. These classes serve to combine common Bluetooth functionality and data needed across all Bluetooth devices. | If the instrument being added is a Bluetooth device, the you should extend com.agtek.location.bluetooth.AbstractBluetoothDevice instead of the normal LocationDevice and the Provider should extend com.agtek.location.bluetooth.AbstractBluetoothProvider. These classes serve to combine common Bluetooth functionality and data needed across all Bluetooth devices. |