As I think of Leo as a file system, the primary conceptual issue so far is the lack of a "root"
rootPosition() returns the first top-level node, but that's not "root" in the fs world, root can't have siblings. You need to be able to descend from root and see all nodes. Currently I'm requiring a single top-level node in my Leo files, which works fine, but is a bit artificial. Could (or does) Leo offer a place to call iter_children() from and get the top-level nodes back? Thanks, Kent -- 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.
