search

OCR4all / LAREX

A semi-automatic open-source tool for Layout Analysis and Region EXtraction on early printed books.
MIT License
177 stars 33 forks source link

Add optional autosave for GT and segmentation #300

Open alexander-winkler opened 2 years ago

alexander-winkler commented 2 years ago

This is a very generic question, probably related to #226 .

I occasionally face text loss during GT production and still lack a precise idea of how saving GT/writing GT to PageXML works in LAREX.

Looking at the console output in my browser, I assume that by hitting Enter/deselecting the input is stored in the variable (actions.js:654) and the Save result button writes changes in all pages to the file(s) (communicator.js:11/13). Is this correct?

Are there any other rules/events that cause the data to be saved, e.g. every n seconds, when changing the page etc.? If not, is there any reason not to have them? The mandatory use of "Save result" for saving changes is a bit cumbersome and I regularly forget saving, especially when working on several pages at the same time. An automated saving would be very helpful at least for my workflow.

Thanks!

maxnth commented 2 years ago

Looking at the console output in my browser, I assume that by hitting Enter/deselecting the input is stored in the variable (actions.js:654) and the Save result button writes changes in all pages to the file(s) (communicator.js:11/13). Is this correct?

Yes, correct.

Are there any other rules/events that cause the data to be saved, e.g. every n seconds, when changing the page etc.? If not, is there any reason not to have them? The mandatory use of "Save result" for saving changes is a bit cumbersome and I regularly forget saving, especially when working on several pages at the same time. An automated saving would be very helpful at least for my workflow.

Adding optional autosave seems very reasonable and useful indeed. We're currently internally rewriting and modernizing the OCR4all / LAREX back-end and front-end to ease adding several large new features (e. g. flexible integration of different OCR / DLA processors as service providers) and to allow more agile development overall. This means that v0.7 will be the last "legacy" release of LAREX and from now on new features (like e. g. autosave) will only be added to the new version of LAREX and will only be available after the development of v1.0 is finished.