On Wed, Mar 3, 2010 at 12:01 PM, Kent Tenney <[email protected]> wrote: > On Wed, Mar 3, 2010 at 11:53 AM, Edward K. Ream <[email protected]> wrote: >> On Wed, Mar 3, 2010 at 11:15 AM, Kent Tenney <[email protected]> wrote: >> >>> What if each node was a file [in] a Git working tree? >>> >>> Git offers incredibly optimized ways to manage the state of the tree. >>> Leo offers incredibly optimized ways to access and manipulate the >>> contents of the tree. >> >> I'm not following this in detail. True, both Leo and Git work with >> trees. But how does that help Leo?
It would generalize the concept of 'node' from 'component of a Leo file' to 'atom of info', opening it up to all kinds of access / use. It would increase the viability of enriching the nodes with metadata more elegantly and standards compliant than the UA. > > For starters, the Leo file is optimized for collaborative editing, branching > merging, versioning ... > > That's what Git does. > > ... if Leo could provide node=file equivalence. > >> >> Edward >> >> -- >> 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. >> >> > -- 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.
