Old Doclight, as well as other PDF-scanning apps, save documents so that they can be accessed again later. This might be something worth implementing in new Doclight.
Arguments against
- The main reason that feature existed in old Doclight was because it had to make all of the user's data accessible to the worker, and IndexedDB was a decent enough mechanism that also lent itself to this feature. Since new Doclight is fast enough that it can export on the main thread, there isn't a need for IndexedDB to shuffle images to the worker.
- Adding features that other apps have isn't the point of Doclight. Not everyone would want this feature, and for a user that didn't want it, it would be unnecessarily using disk space, especially if they didn't know how to delete old documents.
Arguments for
- It could be useful?
- It would open the door to constructing PDFs on a worker thread instead of the main thread, as old Doclight did. Sure, it's a hell of a lot faster now, but offloading work from the main thread is almost never a bad idea.
As of right now, this will probably be implemented if/when I feel like it.
Old Doclight, as well as other PDF-scanning apps, save documents so that they can be accessed again later. This might be something worth implementing in new Doclight.
Arguments against
Arguments for
As of right now, this will probably be implemented if/when I feel like it.