Scanner status

[PhilippMundhenk]

We have a complete rewrite of the web interface (backend and frontend) in #32 (by @vgarcia007) and a rewrite of the scripts in #48 (by @pedropombeiro). There are two interfaces between the two: 1) calling the scripts and 2) the status of the scanner.

1. is easy to solve, as it just uses the same interface as the scanner driver. This may not be the most efficient though. Would we have a benefit interfacing to python more directly? Big downside would potentially be differing behavior between buttons and web interface.
2. needs solving though: I would imagine the python scripts outputting some data into a file defining the current status (scanning front pages, scanning rear pages, waiting for rear pages, waiting for OCR, others?) which is read by the backend could be an easy solution. Thoughts?

[pedropombeiro]

needs solving though: I would imagine the python scripts outputting some data into a file defining the current status (scanning front pages, scanning rear pages, waiting for rear pages, waiting for OCR, others?) which is read by the backend could be an easy solution. Thoughts?

By the way, the python script is already doing something like this, to store the scanning color mode of the front pages, for reuse on the rear pages.

[PhilippMundhenk]

We could probably directly use this file in the /tmp/ directory...

[PhilippMundhenk]

Turns out with #48, 1) is an issue as well. Probably we should call the python scripts directly, see https://github.com/PhilippMundhenk/BrotherScannerDocker/pull/48/files#diff-08f2dd93c39282da1dad194b2cf29b6956b3a906ea9c286ed43d65e8d42b7bac