Mercurial > code > home > repos > light9
diff bin/rdfdb @ 815:d7f1f868eb6c
toplevel window pos is saved in the graph. Patch conflicts no longer break as hard, but they don't exactly reset themselves right yet eiher
Ignore-this: 56f96fd0b1a8602abc4e41851685794c
| author | drewp@bigasterisk.com |
|---|---|
| date | Sat, 20 Oct 2012 21:52:10 +0000 |
| parents | 1ae8e6b287e3 |
| children | 295b867fd810 |
line wrap: on
line diff
--- a/bin/rdfdb Sun Sep 30 07:11:49 2012 +0000 +++ b/bin/rdfdb Sat Oct 20 21:52:10 2012 +0000 @@ -16,7 +16,12 @@ A caller can submit a patch which we'll persist and broadcast to every other client. -Global data undo should probably happen within this service. +Global data undo should probably happen within this service. Some +operations should not support undo, such as updating the default +position of a window. How will we separate those? A blacklist of +subj+pred pairs that don't save undo? Or just save the updates like +everything else, but when you press undo, there's a way to tell which +updates *should* be part of your app's undo system? Maybe some subgraphs are for transient data (e.g. current timecode, mouse position in curvecalc) that only some listeners want to hear about.