Hi folks, I've thought on and off about the merits of a Leo implementation that stores its nodes and outlines, not in .leo files, but in an SQL database (MySQL, PostgreSQL, SQLite etc).
The idea is to allow for nodes to be cloned across different outlines, not just cloned at different points in the one outline. This would also allow for multi-user access, that is, if there is a protocol for "locking" and/or "sharing" nodes. Another option, which doesn't require database implementation, would be to allow for a node type which allows nodes in one .leo file to ref nodes in other .leo files. For example, file1.leo has a node /foo, with a child node /foo/bar which actually references a node /baz/bar in file file2.leo The basic idea is to allow one outline to reference nodes in another outline (or reference the entire outline). Thoughts? Cheers David -- 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.
