On Tue, Jan 3, 2012 at 5:36 AM, Offray Vladimir Luna Cárdenas <[email protected]> wrote: > > Thanks. About implementation my idea is to start with a different approach. > The idea is to "teach fossil to Leo" and having in that way a default > support for versioning and collab in Leo, so the convention for working > together in a collaborative p2p fashion that I showed would be automatically > supported by Leo + Fossil. Adding an external file to Leo would add it to > the Fossil repo and all the commands for working with Fossil would be > supported inside Leo and so on. Then I will try to deconstruct the Leo data > structure, if this is needed, so it can be supported by the NoSQL database > or the DAG of Fossil. So the idea is to have a particular implementation of > collaboration + versioning that may be abstracted later to work with more > approaches.
But if there was a database representation of the Leo document already, with code for saving that plus putting it back into Leo, wouldn't that give you the information and/or understanding you need to demonstrate your approach? Including seeing where in the code to teach Leo? My impression is the only thing that keeps people from going ahead with what you propose, or demo'ing any approach at all, is uncertainty about having an adequate model that works with Leo's intricacies. Seth -- 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.
