Thread: auto-save?
View Single Post
Old 12-07-2015, 09:58 PM   #11
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by BetterRed View Post
If you mean autosaving over the top of the original then I couldn't agree more - but is there any 'widely used' software that does that in this day and age. Notepad++ does what Word does without the Recovery leg. The auto-save files have recognisable names including a timestamp so Recovery 'relatively' easy.

By 'widely used' I'm referring to software that's used by more than just the person who wrote it and their besotted (browbeaten) family members
Well, I can't really think of many programs that do autosaving.
I didn't even know Notepad++ did it -- and I see that is via a plugin.


Saving lots and lots of timestamped autosave files would be a waste of space IMHO. You only need the last version.

Quote:
But to me the main issue with auto-saving a 'package' like an EPUB is what gets auto-saved. Should all the files be bundled up into 'new' package that could be profoundly invalid, or should it be just the components that changed since last save. Either way is fraught with difficulties. And IMO, on that basis alone, the developers would be justified into putting it into the 'too hard' basket.

BR
Not sure what this is supposed to mean.

Presumably, the whole point is to save all changed components.
And saving the non-changed components is a no-op.

What difficulties do you see -- in either case?
eschwartz is offline   Reply With Quote