On Sun, 8 Jan 2012 07:59:20 -0500 Seth Johnson <[email protected]> wrote:
> On Sun, Jan 8, 2012 at 5:58 AM, Seth Johnson <[email protected]> wrote: > > http://bazaar.launchpad.net/~leo-editor-team/leo-editor/trunk3/view/head:/leo/core/leoFileCommands.py > > . . . and I see where Ville got his nodes and edges db representation: > XML files are trees, and that's one way to store them. I'm going to > need to figure how to plug in something where other approaches to > doing sax and xml in databases presuppose a specific db > representation. A dbxml in which I code the db writes myself. What would be easier than making Leo load from scratch from a DB would be making scripts which, with a regular Leo file already loaded, at the user's prompting, import / export from / to a DB. That would let you get to proof of concept demo faster without dealing with the extra details involved in loading an outline completely from the DB, where you have to untangle the outline creation and data loading components. Cheers -Terry -- 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.
