Thomas writes: I've been thinking that there should be a book on Leo. I don't think I've got another book left in me, but I'm not completely happy with the existing docs because I don't think they really match what a new user faces when trying to fire up Leo and use it the first few times.
I'm a new Leo user -- I've been programming in Python for 5+ years, but somehow only recently managed to discover it -- and think something like this would be very helpful. The tutorials, documentation, and Edward's YouTube videos are great. But what I think might be really useful are some step-by-step examples of common user stories. For example: * I'm a developer working on a small-ish Python project that I collaborate on with other people. How can I effectively use Leo to start editing my existing code base? How should I go about breaking up parts of the existing code into an outline (without actually breaking things)? * I'm a technical writer working on a publication. How can I start writing my outline in Leo, and then save/export it to be shared with others in a plain text format (ReST, Markdown, etc.)? * I manage a small website that's mostly just HTML and CSS. How can I use Leo's outlining framework to keep things more manageable and reduce duplication? Those are just some ideas. And I apologize in advance if these things *should* be obvious to a newcomer. I've climbed a few text editor hills (vim, Emacs, acme, etc.) and I really like what I've seen of Leo, but I do find myself puzzling at what seem like basic questions. Thanks all. Ben -- 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/ae892918-9a16-4427-a019-b2e7e318835an%40googlegroups.com.
