<div class="gmail_extra"><div class="gmail_quote">On 7 November 2012 12:43, Tom <span dir="ltr"><<a href="mailto:tmbdev@gmail.com" target="_blank">tmbdev@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
(I think lack of autosave should be prio-blocker.)</blockquote></div><br>In general, I don't think we'd block on a new feature. The standard for setting a blocker is 'would we wait for this if everything else is ready for a release?' 0.14 will improve on 0.13 even if it's released without autosave, so it wouldn't make sense to hold it up for that.<br>
<br>Could you flesh out a detailed description of how an autosave might work, perhaps as an IPEP (<a href="https://github.com/ipython/ipython/wiki/IPython-Enhancement-Proposals-%28IPEPs%29">https://github.com/ipython/ipython/wiki/IPython-Enhancement-Proposals-%28IPEPs%29</a> ). It should describe, for instance:<br>
- What gets saved<br>- Will it be always on, configurable, or 'smart'?<br>- Where does it get saved? I don't like extra files cluttering up my working directory.<br>- What happens if I have the same notebook open in two tabs? Or two computers talking to the same server?<br>
- Notebooks needn't be stored as files, they could be blobs in a database - how will this be abstracted away from the frontend?<br>- Will autosave files be automatically removed, and if so, when?<br>- How is a crash detected, and what UI presents the autosaves to the user?<br>
<br>Looking at this differently, I wonder if we could use the localStorage Javascript APIs to do autosaves client-side? I suspect that idea has its share of difficulties, but perhaps it's worth exploring.<br><br>Thanks,<br>
Thomas<br></div>