On Thu, Apr 10, 2008 at 5:05 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
> > Here's a stopgap measure to survive 2 people editing the same .leo > > file, with very little coding > > I'm not sure I understand the problem you are trying to solve. Two people editing the same .leo file in network share. There is no version control system involved. > bzr will warn about conflicts in .leo files. In a collaborative > environment, all data should be in thin derived files. The "reference" .leo That's too much overhead for an outline/mindmap/whatever. This is not really about programming tasks. > files hardly ever change, the corresponding local .leo files can have > whatever people want. Yeah, but here the reference leo file is all there is. > Perhaps more importantly, Leo's compare-leo-outlines command was designed to > handle cvs conflicts. It compares the present outline with another, and > creates clones of all inserted, deleted and changed nodes. Might this be a > good starting point for you? Yes, sounds like it. -- Ville M. Vainio - vivainio.googlepages.com blog=360.yahoo.com/villevainio - g[mail | talk]='vivainio' --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
