On Thu, Mar 1, 2018 at 4:21 PM, Matt Wilkie <map...@gmail.com> wrote:

​> ​
What's the practical limit for number of nodes in Leo?

​Good question.  I don't know the answer in all its details, but here are a
few ideas:

1. Leo now supports representing outlines as sqlite databases, with .leo.db
extension.  See this post
Afaik, there are no practical limits to such db's nor are there limits in
Leo's ability to access them.

2. Leo uses ​Python's sax parser to parse xml.  This is likely to be
significantly slower than using sqlite-based code.

3. Leo scans the outline after loading it, looking for @<file> nodes.  This
code skips @ignore trees, so you would want to put the entire outline tree
under an @ignore directive.

4. Leo's tree drawing code would likely choke on showing more than a few
thousand nodes.  There are several ways around this.  First, one could
access the dictionary in a null gui, say from the Leo bridge.  Or one could
hide the dict so that it never gets redrawn.

In short, it should be possible to represent a very large outline as a
sqlite (.leo.db) file.


You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to