On Thu, Aug 5, 2010 at 2:00 AM, Gour D. <[email protected]> wrote: > Moroever, I'd eliminate and/or rearrange some more stuff...
I really do not think this is the important issue. Leo's wiki is, or could be, a great place for users to share ideas. Leo's official docs are the key to learning Leo, imo. I stayed up writing docs until 2a.m. last night because I was excited about sphinx's indexing capabilities that I learned how to use yesterday. The total rewrite of chapter 4, combined with truly integrated glossary and index should help newbies considerable. Last night I saw how to solve a minor problem with the index: It gives entries such a section reference [1] [2], with no indication of where the primary link (section reference) or the second links ([1] and [2]) lead to. Maybe css could provide help, but instead I'll use the following convention: .. index:: x (t) for tutorial entries .. index:: x (r) for reference entries .. index:: x (g) for glossary entries .. index:: x (n) for entries in any other chapter n. So the index entry for section reference will look like this: section reference (7) # Scripting Leo with Python section reference (g) section reference (r) section reference (g) The plan for these kinds of entries is as follows: - The tutorial will be the most friendly description of a feature. - The reference item in chapter 4 will be a concise description of everything there is to know about a feature. - The glossary item will be a concise summary of a feature. This should get the job done for almost any user. 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.
