Hi,
On 10/04/11 10:19, Edward K. Ream wrote:
On Mon, Oct 3, 2011 at 7:46 PM, Edward K. Ream<[email protected]> wrote:
A Modern Undo - Making undo usable beyond the last few changes
http://e-texteditor.com/blog/2006/making-undo-usable
Thanks for this. I've put it on the list of things to consider.
Surely, a better undo would help us all.
Reading the comments about a "better" undo, my first impression is
that it is indeed too complicated. Again, my first impression is
simply that bzr (or whatever) provides the needed granularity. And
Leo provides an easy way of coping snapshots of a particular node. I
typically move nodes that I am about to delete forever to the "unused"
tree in leoNotes.txt, and that provides another kind of backup.
Undo is actually a hard problem because people don't visualize
(temporally) branching structures easily, especially for small units
of change.
Edward
This kind of connection between a portable and minimalist SCM/VCS and
Leo is what I'm trying to communicate about the bridge between Leo and
Fossil. Not being a developer myself made this kind of idea fussy when I
said this only in words and not in code... I will try to code something,
but meanwhile (because learning to code will not be a trivial task) I
can push my explanation with more words, if this is needed.
Cheers,
Offray
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
