comparison 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
comparison
equal deleted inserted replaced
814:1ae8e6b287e3 815:d7f1f868eb6c
14 callers faster. 14 callers faster.
15 15
16 A caller can submit a patch which we'll persist and broadcast to every 16 A caller can submit a patch which we'll persist and broadcast to every
17 other client. 17 other client.
18 18
19 Global data undo should probably happen within this service. 19 Global data undo should probably happen within this service. Some
20 operations should not support undo, such as updating the default
21 position of a window. How will we separate those? A blacklist of
22 subj+pred pairs that don't save undo? Or just save the updates like
23 everything else, but when you press undo, there's a way to tell which
24 updates *should* be part of your app's undo system?
20 25
21 Maybe some subgraphs are for transient data (e.g. current timecode, 26 Maybe some subgraphs are for transient data (e.g. current timecode,
22 mouse position in curvecalc) that only some listeners want to hear about. 27 mouse position in curvecalc) that only some listeners want to hear about.
23 28
24 Deletes are graph-specific, so callers may be surprised to delete a 29 Deletes are graph-specific, so callers may be surprised to delete a