Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.programming    |    Programming issues that transcend langua    |    57,431 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 55,670 of 57,431    |
|    Julio Di Egidio to Ben Bacarisse    |
|    Re: Undo / Redo design pattern.    |
|    04 Apr 22 18:53:21    |
      From: julio@diegidio.name              On Tuesday, 5 April 2022 at 03:25:43 UTC+2, Ben Bacarisse wrote:              > This is just a random observation that might trigger something useful in        > more complex situations...        >        > Emacs has what I find to be a very useful refinement of undo/redo: it        > can be limited to a region of the text.              Maybe worth noticing in this context (see the original question) is that those       are already applicative details: a generic undo/redo engine just handles       opaque path/value pairs, what's encoded in those paths and values is       application specific. Then of        course one might think of abstracting a little bit on the cases for the paths       and values in various scenarios (from a text editor to a database manager to a       designer and what not: whether they have something in common), but this would       be a different and        further layer of abstraction, and I haven't yet thought about it at all, but       my guess is that this isn't worth it, as there isn't much here in terms of       actual generality and shared logic. That's also an example of what in real       production rather comes        out incrementally, as long as the architecture is at every step rational...              Julio              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca