[IPython-User] PLEASE make autosave standard
Tue Nov 6 17:39:25 CST 2012
Just for the record: Ctrl-S saves on Chromium on Lubuntu.
Google Docs autosaves with almost every change and it works really badly
for me. Everyone has there own take on these UX elements. I vote for Trust
the Developer - if they want stuff saved, they should say so.
On Nov 6, 2012 11:24 PM, "Tom" <email@example.com> wrote:
> "You might like autosave, but I personally often want to revert to my
> last saving point. Then autosave is really annoying for me, I am not the
> only one."
> I don't care about autosave per se. What I care about is that a tool that
> I spend hours in every day and recommend to others is robust against
> failures, like all the other tools I use regularly: I should be able to
> pull the power plug on my computer and not lose more than a minute or so of
> work even if I never saved anything.
> "If you came up with a good patch, we'll be happy to see you open a Pull
> Request on github that improve situation."
> It is impossible to come up with a "good patch" under the constraints you
> list. The question is whether those constraints are more important to the
> iPython developers than preventing data loss.
> On Wed, Oct 31, 2012 at 12:27 PM, Matthias BUSSONNIER <
> firstname.lastname@example.org> wrote:
>> Le 31 oct. 2012 à 11:53, Tom a écrit :
>> > I just lost an hour of work again because Chrome and iPython notebooks
>> conspire against me.
>> Sorry about that,
>> > iPython notebooks take forever to complete when there is a lot of
>> output. This is really a problem by itself. Saving iPython notebooks
>> requires navigating with the mouse to click on a tiny button somewhere at
>> the top; this is distracting and interrupts work. There is no keyboard
>> Ctrl+s should save in some browser/os
>> Ctrl+m, s should always do.
>> It is in the doc, and on the keyboard shortcut help (C-m,h)
>> If it does not work, bug report.
>> > Chrome compounds the problem by popping up a dialog box every few
>> seconds asking whether I want to kill the page (and hence lose all my data)
>> or continue.
>> Why is that ? It shouldn't. Which version of chrome do you have. Which
>> version of IPython ?
>> Is it the "this page/script have stop responding message ?" I never had
>> it with IPython notebook.
>> You can open a bug report and we'll try to figure out why this happen,
>> this should make your workflow a lot easier.
>> the entire page. (I think Firefox has other problems, which is why I don't
>> use it.)
>> > Asking me to confirm throwing away hours of work that are on the screen
>> and in memory and should be trivially savable really adds insult to injury.
>> > It's a conspiracy of multiple usability problems in iPython and
>> Chrome, any of which should be easy to fix for the developers.
>> You might like autosave, but I personally often want to revert to my last
>> saving point.
>> Then autosave is really annoying for me, I am not the only one.
>> A persistant notebook without having to explicitly save is not that easy.
>> Hacking something that does the job most of the time is not that hard,
>> but doing it the right way, not so much.
>> * Consider fact that some people do not use the notebook on
>> localhost and hence saving might be **very** bandwidth consuming.
>> * Same notebook can be opened several times constantly
>> overwriting each other if autosave is on.
>> * Oops I deleted this cell... I just have rollback to previous
>> save version.... Too late....( no we can't Ctrl-Z cell deletion yet)
>> * Current API does not allow to save with another name, people
>> rely on our API, we can't change without deprecation warning first.
>> * None of us are real js developers, all of us work on our little
>> free time freely on IPython.
>> * we would like to differentiate persistence/saving/version
>> You can have a look at Min's extension to autosave.
>> Using custom js in your profile on 0.13+ it shouldn't be too hard to
>> enable autosaving by default.
>> Ask if you need help, but with above extension and docs, it shouldn't be
>> too hard to figure out.
>> If you came up with a good patch, we'll be happy to see you open a Pull
>> Request on github that improve situation.
>> You can also help by reviewing/testing the current opened PR so that
>> we'll get more time to work on new stuff like autosaving.
>> Hope we'll solve most of your issues.
>> > Tom
>> > _______________________________________________
>> > IPython-User mailing list
>> > IPython-User@scipy.org
>> > http://mail.scipy.org/mailman/listinfo/ipython-user
>> IPython-User mailing list
> IPython-User mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-User