Open GoogleCodeExporter opened 8 years ago
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
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
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
Original issue reported on code.google.com by
rayner...@gmail.com
on 25 Sep 2009 at 8:45