44 |
Past: |
Past: |
45 |
----- |
----- |
46 |
|
|
47 |
2003-05-25 [3.5h, 13.30-14.15, 14.30-17.15]: |
2003-05-25 [3.5h, 13.30-14.15, 14.30-19.00]: |
48 |
|
|
49 |
- think about article |
- think about article |
50 |
- integrate Storm with Emacs, so that clicking a text/plain |
- integrate Storm with Emacs, so that clicking a text/plain |
54 |
versioning, with only storing diffs and with merging |
versioning, with only storing diffs and with merging |
55 |
after concurrent edits on two different computers, |
after concurrent edits on two different computers, |
56 |
and then we're talking ;-) |
and then we're talking ;-) |
57 |
|
- more thinking about pointers: creating a pointer scheme |
58 |
|
we can make the persistency commitment on is extraordinarily |
59 |
|
difficult. can we somehow protect a document so that |
60 |
|
old versions are still retrievable after a key has been |
61 |
|
revoked? -- if we had timestamping, one approach may be |
62 |
|
that when the key for a document is revoked, the document |
63 |
|
is frozen: all the old versions can still be retrieved, |
64 |
|
but the document cannot be updated. but that, again, |
65 |
|
needs timestamping... |
66 |
|
- an idea that may actually work: integrate the Storm stuff |
67 |
|
with ReST: edit as reStructuredText, browse as HTML. |
68 |
|
This could give us versioning *and* browsing, the latter |
69 |
|
being important when going beyond a single system. |
70 |
|
Needs thinking about how to integrate this well w/ pointers. |
71 |
|
|
72 |
2003-05-24 [8h, 13.45-17.00, 19.30-19.45, 20.00-0.00]: |
2003-05-24 [8h, 13.45-17.00, 19.30-19.45, 20.00-0.00]: |
73 |
|
|