On Wed, Feb 24, 2010 at 3:14 PM, Ville M. Vainio <[email protected]> wrote: > Unfortunately my freetime has disappeared for a prolonged period, > however, I thought I would dump the stuff I *would* do if I had some > (I know this is not immensely helpful):
> * SQLite .leo file format (medium) > > - Able to attach huge binary data to .leo file without increasing load > time (images, etc). This would be done by lazy loading of bodies - for > certain node types body is not fetched unless leo requests it. The > data would still be contained in self-contained form in the leo file. > - Able to open multiple "views" on the same leo file (in separate leo > processes), and actually be able to save without clobbering the edits > done in other leo instances (tentative) > > If the previous is too "hard core", an alternative > > * zip .leo file format (easy/mediem) Have you looked at Leo's support for Zope's zodb database? It's confined to leoNode.py, iirc. That might be a starting point. I'm not sure the zodb stuff has ever been used "for real". I suspect it is buggy, or even broken. In general, I like this idea. It's certainly worth a try. 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.
