Open teolemon opened 1 year ago
If we were to switch to camera
and defer to that for the texture, we'd have to drop MacOS support, since it's not a supported platform.
However, we could try to use our MacOS implementation as a starting point, to get things landed over there.
As a side benefit: camera_windows
exists, but I'm not sure if its feature is complete enough yet.
I also don't know if Windows has a library for scanning barcodes.
I think that this can be a lot easier to implement once we have the platform interface work set up. See https://github.com/juliansteenbakker/mobile_scanner/issues/401
Then we can rely on camera_android_camerax
for the Android implementation, but keep our own implementations for iOS/MacOS as-is (since it only affects Android then)
What
Google announced a newly released camera_android_camerax (0.5) pub.dev package which switches camera to CameraX (there are still a LOT of things missing, like flash, focus…, but they announce their intention to implemeent it eventually). Overtime, it could reduce maintenance cost of mobile_scanner, and custom code.
It might be worth weighting advantages and effort, and investigating switching to camera_android_camerax https://pub.dev/packages/camera_android_camerax