I don't think anyone is going to do much more documentation - and it would be hard to organize in a way that is both helpful and practical to search.
> if you want to do some Sphinx-style documentation > Actually, I discovered the existence of Sphinx as a side effect of my discovery of leo. Leo is so large, complicated, and flexible, it can be hard to track down > the information you need > That statement is a little bit in contradiction with the main marketing message ;-) Not that I disagree. > I don't think anyone is going to do much more documentation > I hope you will be proven wrong, because this is one of the thing that limits leo's popularity. At least core-developers should know it. Of course, then they are free to care or not. > Really, there's a need for a Leo book. I have no idea who would be > willing and knowledgeable enough to write one. I don't know enough, and > anyhow I don't have another book left in me. > I know definitely less, and I never wrote a book. But for an "outliner", the inexistence of _any_ book is strikingly paradoxal, isn't it ? Shouldn't starting "the (outline of the) Leo book in leo" be a trivial task for any of the core contributors ? (Just kidding) But it can be very rewarding when you finally get some piece of code that > does something you need but that doesn't seem to exist. > That's the worst : it may exist, but you (at least I) don't know it. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/b7d0f385-187f-4cef-bacc-9ecbf0665d5bn%40googlegroups.com.
