I am creating a sqlite storage support for leo. Motivation for this is that I'm going to do a mobile client that needs to be able to handle large leo documents in restricted amount of memory; xml file + reading all nodes to memory at one time doesn't scale for that.
The idea is that I have all body contents in sql file. There will be no support for @file et al in the mobile client, I just dump the bodies as-is to the one "leoq" file (the file extension I plan to use). I also plan to dump referenced data like images, local files, etc. to the sqlite database. This wouldn't be sensible in xml file (it would make reading in the file very slow, as well as memory consuming). You can explore the thing by looking at ideas.leo => mobile.txt in contrib branch. You can press ctrl+x on "Creation" node, then "Browser". For reference, here's how I do the tree dump: https://gist.github.com/912584 I adapted the sql schema from here: http://techportal.ibuildings.com/2009/09/07/graphs-in-the-database-sql-meets-social-networks/ I plan to add support for this format as an "export" option, not regular file saving functionality. The idea is that you export the leoq file from a document on your desktop, then send the self-contained leoq file to your mobile client (phone / tablet) for offline browsing. I might be able to make this a commercially useful solution (i.e. you can sell hierarchical "leo books" in app stores), but we'll see about that ;-). I also plan to implement zip compression for message bodies exceeding certain length. -- 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.
