Closed nflorin closed 2 years ago
This will involve a reasonable amount of new code and fiddling with the existent code, so I'm marking it as low priority until/unless we decide making a complete GUI version is a high priority.
I now think this isn't really necessary, so closing.
The checks process as it is now runs as a single process, printing occasional updates to the screen. In a GUI, this would mean that whatever screen opened when the process started would remain frozen in place for however long the process needed to run. This would not be acceptable to any run involving more than a couple of thousand records that have already been downloaded from WorldCat. If the process is run in a separate thread (or possibly a new process) with communication back to the front end via a queue then we should be able to keep the GUI updated.
This will require changing the backend and updating the text front end.