164 - Extract camera scanner from core library #175
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
scanner-camera
, which contains all camera-related classes (camera SDK and camera activity)ScannerCompatActivity
: remove all camera-related mechanisms (goToCamera
,layoutIdCamera
,cameraViewId
,cameraScanner
) and camera-specific permissions. All these mechanisms are inside a new activity .CameraCompatActivity
inscanner-camera
(com.enioka.scanner.sdk.camera
), that contains a basic layout for the camera, as an Android activity. Contains the entire camera part previously located inScannerCompatActivity
.Change inside
ScannerCompatActivity
:ScannerCompatActivity
can automatically or manually (with a toggle button) fallback to theCameraCompatActivity
via an explicit Android intent if the maven artifactscanner-camera
is included, otherwise there is no camera-as-scanner functionality.It is now possible to use only the default camera activity layout without the scanner activity layout.
The entire camera scanner API is still accessible, via the
scanner-camer
artifact.