On Aug 9, 8:05 am, "Edward K. Ream" <[email protected]> wrote: > I'll be working next on Chapters 2 and 6, including the nutshell. I > hope to conclude all the documentation work in a few days. There are > urgent programming tasks on the list.
Two new projects have "appeared" recently. I plan to explore them asap. 1. Simplifying @rst. As Leo's docs themselves show, it *is* possible to do simple things simply with @rst trees. However, the plethora of options is a symptom of lack of fundamental power. The distinction between code and doc modes is a truly ugly hack. The recent Doh! moment (@rst trees in LeoDocs.leo only need to generate intermediate files) might lead to simpler, more-powerful- because-more-general, alternatives. We shall see. 2. Using zodb as Leo's cache. leoNodes already contains the low-level code to do this. I'm going to revisit the caching code soon--it might be the time to re-imagine caching as a front end to zodb. That might allow Leo outlines to contain (that is, connect with) millions of nodes... 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.
