Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

New and Improved!

Our Engineers have meticulously rewritten our Anyline Android SDK from the ground up with version 43.0.0. Here you will experience a wide array of game changing features, performance enhancements and overall ease-of-use improvements.

This article covers a summary of what v43.0.0 offers compared to our previous versions, a video guide on how to upgrade from any previous version of our Anyline Android SDK to v43.0.0, links to the documentation, and a glossary of some of the terminology associated with our SDK.

Before and After

Previous versions of Anyline SDK

Version 43 of Anyline SDK

Changes in Version 43.0.0

Anyline Android SDK previous versions

 Initializing the plugin

Implementing a scan use case requires the following classes to be initialized:

  1. a scan view

  2. a scan view plugin

  3. a scan plugin

the second and third class specify the scanning use case you have selected.
For example:
OCR → OcrScanViewPlugin AnylineOcrConfig

 Composite plugins

The id of the root node’s JSON property is more use-case specific.

For example, "id": "meter_barcode_parallel_scan".

cancelOnResult is a required field and is either true or false. id should be a valid keyword string and is a required field. viewPlugins is an array where the viewPlugin JSON bodies of each child plugin is listed.

 JSON Config File Structure

Previous config files are parsed with the top-level keys identified as the objects they represent.

For example: The JSON configuration for the camera on a device is under the key identifier, camera ; the JSON configuration for the flash of the camera is under the key identifier, flash, and so on.

The cancelOnResult method is found inside the viewPlugin

 Listeners

The ScanPlugin, ScanViewPlugin, and ScanView delegates all require the implementation different listeners for specific use cases.

Some use case specific delegate examples are OcrScanResult, LicensePlateScanResult, and so on.

 Result Type

ScanResult does not support strongly-typed result types of use cases and are not defined as part of the result object.

Anyline Android SDK v43.0.0

 Initializing the plugin

Only the ScanView and ScanViewPlugin need to be initialized, with an appropriate ScanPlugin being generated by the ScanViewPlugin when the configuration for the target use case is passed.

Furthermore, the scan view config is now initialized together with its scan view plugin.

 Composite plugins

 JSON Config File Structure

New config files are parsed with the top-level keys identified both as the objects they represent and with the key name “config”.

For example: The JSON configuration for the camera on a device is under the key identifier, cameraConfig ; the JSON configuration for the flash of the camera is under the key identifier, flashConfig, and so on.

The cancelOnResult method is found inside the pluginConfig.

 Listeners

The ScanPlugin, ScanViewPlugin, and ScanView listeners* have been altered, with the removal of implementing different use case listeners. This has resulted in a more focused and efficient interface with more time-saving features.

Use case specific delegates such as OcrScanResult, LicensePlateScanResult, etc., are now removed and replaced by a single class: ScanResult.

 Result Type

ScanResult now supports strongly-typed result types of use cases and are defined as part of the result object.

This means that for any use case you are scanning (for example, OCR), then the use case result (in this case, ocrResult) will be a non-null property where you will be able to find the result.

Upgrading to v43.0.0

A video tutorial guide will be provided soon, please check back for updates.

Other Additions

  • Added PluginResult for describing result data

    • Added a type of plugin result for each scanning capability

  • [Tire] Added tire size specification fields to the result

  • [Barcode] Added AAMVA parsing for PDF417 codes on driving licenses

  • [ID] Restructured ID results in a way that every field can contain date- & multi-language information

Links to Documentation

If you require any further information or details on our v43 upgrade for the Anyline Android SDK,
please click here to see our documentation page.

Glossary

Please Note

*Listener - Refers to the class that adheres to an interface and implements methods contained within the interface

*Composite Plugin - Running a composite plugin either sequentially or simultaneously puts more than one discrete plugin to work. There are two modes which one can use:

  • sequential mode: for example, your workflow requires you to scan a license plate, and then a VIN. This is almost like running two separate scan plugins one after another, but with a composite you get the combined result of the two when you finish scanning both.

  • parallel mode: you are running two or more plugins simultaneously. (For example an ID card with a PDF417 barcode in it). You get the chance to scan both, and again the results are presented when you are done.

  • No labels