CloudPOS SDK: Difference between revisions
(→C API) |
|||
| Line 13: | Line 13: | ||
=== JNI API === | === JNI API === | ||
wizarPOS offer JNI interface to wrapper the C API to help the developer to use C API. Now we recommended you to use Java API instead of JNI API. | |||
*[http://{{SERVERNAME}}/jniinterfaceapi/ API Spec] | *[http://{{SERVERNAME}}/jniinterfaceapi/ API Spec] | ||
*[[How to import JNI to a project]] | *[[How to import JNI to a project]] | ||
Revision as of 09:25, 22 November 2018
Device API
There are three layers of device API, the lower layer is C, the device provides C interface, and the third-party app writes their own JNI source by calling the C interface. The middle layer is JNI interface, wizarPOS writes JNI source and generates the device so files, so the third-party app just uses the JNIInterface to finish the calling. The upper layer is Java interface, wizarPOS provides Java interface for the third-party app, the third-party app only needs to import the .aar pakcage to their libs. The app should request permissions in manifest file.
- Permissions defination
- WizarPOS printer ESC commands
C API
The C API offers header files definition and the relevant so library is already included in the system. The application developers can create the native so library by the C API to implement their business logic. So the implementation will be more secure than Java implementation.
JNI API
wizarPOS offer JNI interface to wrapper the C API to help the developer to use C API. Now we recommended you to use Java API instead of JNI API.
Java API
We packaged all the implement and resources to an aar file, so your project only need to add the aar file to your libs. You can always download the latest aar file from below. Because the aar file in SDK or in samples sometimes are not latest one, so after you download the sample, you should replace the aar to the latest one.