On Aug 2, 1:26 pm, "Edward K. Ream" <[email protected]> wrote: > On Mon, Aug 2, 2010 at 12:09 PM, thyrsus <[email protected]> wrote:
> Leo's compare-leo-files command compares two outlines created by the > .leo files. Diffing Leo outlines (rather than the xml that generates > them) is a snap because every node has a gnx! Thus, discovering > inserted and deleted nodes is trivial, and diffing changed nodes is > just a matter of comparing headline and body text. > > However, the problem of understanding the diffs still remains. It's a > human interface problem. > Yes! Thanks for emphasizing the compare-leo-files command. That, combined with a human interface for change reconciliation, perhaps hinted at by the Recovered Nodes techniques, is what I need for collaboration. Or there may be some magic in Google wave's eventual consistency/ operational transforms (http://arstechnica.com/open-source/news/ 2009/07/google-releases-wave-protocol-implementation-source-code.ars), topics which I believe were addressed by Rodrigo Benenson in the proposals for LeoN. Perhaps the trick will be to get Google excited about Leo ;-). I've never learned interface design; it's always been a gift from the gods for me - that is, the result of someone else's talent and hard work. - Stephen -- 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.
