Offline and Online Fail-proof saving

[GoogleCodeExporter]

Please introduce dual saving functionality - both offline and online.

Introduce additional offline saving. Save to a temp file the contents of
the currently edited text once each X (1-N) seconds of idle and upon each X
(1-N) characters typed. Upon relaunch after crash (any exit other than
manual exit), recover contents from temp file.

Original issue reported on code.google.com by rayner...@gmail.com on 25 Sep 2009 at 8:45

[GoogleCodeExporter]

Added to Nocs 2.0 suggestions - might be slightly complicated to implement 
though.
Thanks for feedback!

Original comment by mikko.junnila on 25 Sep 2009 at 11:01

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Actually for small documents saving each 2-4 characters shouldn't be 
problematic at
all, and you could enforce slowdown of character-based saves for documents over
certain size in kilobytes. 

By the way when I say enter Character-based chars, few details should be taken 
into
account, that somewhat complicate the model without making it excessively hard 
to code.
1. Count clicks that move the pointer as types characters.
2. Count arrow movement of pointer as typed characters but on a multiplied 
number of
arrow presses per save. 
3. Remember exact location of pointer in the text. When recovering a text from 
the
buffer, place pointer at the last remembered place.
4. When starting Nocs again after-crash, auto-recover the temp document. 

Original comment by rayner...@gmail.com on 25 Sep 2009 at 11:25

[GoogleCodeExporter]

and what if internet down or google docs down :) make it auto-save offline file 
for temp

Original comment by alie...@gmail.com on 2 Jul 2010 at 4:30