Re: v6: still no multiple undo?
- To: mathgroup at smc.vnet.net
- Subject: [mg77450] Re: v6: still no multiple undo?
- From: David Reiss <dbreiss at gmail.com>
- Date: Sat, 9 Jun 2007 05:29:46 -0400 (EDT)
- References: <firstname.lastname@example.org>
In WorkLife I have implemented an execution log that retains all of the cells that one executes in a mathematica session if that execution is done though the appropriate palette button. See http://scientificarts.com/worklife/documentation/evaluationpalette.html I was wondering last night whether I can, in Version 6, make this an automatic behavior (toggled according to the user's choice) that is done whenever an execution takes place, irrespective of whether the palette button is used. Functoins such as FrontEndEventActions, NotebookEventActions, or CellEventActions may well do the trick. I use these for other purposes in WorkLife, but they are very broad and poserful for other things. I will look into this and let the group know what I come up with... -David http://scientificarts.com/worklife Now Mathematica 6 compatible On Jun 8, 5:50 am, "Barthelet, Luc" <l... at ea.com> wrote: > While I strongly support that multiple undo is a feature we need to see > soon, it will take some real work to get there. > > The editor, and the kernels are linked in an efficient exchange of messages > and information about what needs to be displayed where and when. > > While implementing multiple undo-redo in a stand alone editor usually > requires only to implement a tokenized undo-redo, in the v6 font end, it > will require a more complex model. It is a bit like if you were trying to > implement multiple undo on a wiki site like wikipedia where they are > multiple contributors. > > We probably do not want the kernel to "undo", just the front end. So one > solution would be to make the kernel and the user to appear as a single > contributor, and to undo both effects on the front end. So one undo might > remove an output created by the kernel. > > Even that is challenging, because Dynamics now create a lot of updates and > you will not want to roll those back. > > Anyway, the front end team is obviously smart enough to find a solution for > all those things, but it is not going to be easy. > > A cheap thing that I would like to see, is a text buffer of all my input and > all the code I deleted saved as a log on disk. It might be ugly, but it > would be VERY USEFUL. > > Cheers, > > Luc > > On 6/7/07 3:34 AM, "David Bailey" <dave at Remove_Thisdbailey.co.uk> wrote: > > > David wrote: > >> Will Robertson wrote: > >>> Hello, > > >>> I am baffled that technical software is released in 2007 with only a > >>> single undo level. Am I missing something here? Is it because I'm > >>> using a student license? How hard can an undo stack really be in the > >>> notebook interface? > > >>> I've been irritated a few times in v5.2 from clumsy keypresses losing > >>> me work that I would expect to be two "undo"s away. Alas not. Still. > > >>> Will Robertson > > >> Good point! I've wondered the same thing for a long time. This is the > >> only app I run that doesn't happen multiple levels of undo. I think it's > >> time WRI spent some time on this issue. > > > How much time could it possibly take! Once you have a 1-level undo > > working, all you need to do is spill the relevant data into a structure > > - possibly on disk - and retrieve it as needed! > > > David Bailey > >http://www.dbaileyconsultancy.co.uk