On Mon, Jun 20, 2011 at 7:25 AM, Edward K. Ream <edream...@gmail.com> wrote: > On Sun, Jun 19, 2011 at 2:46 PM, aeromorrison > <adam.morri...@sportplanedesign.com> wrote: > >> We use leo quite a lot here at our company. I would say we are >> moderately technical users, but still have a lot to learn about leo! >> This is the key problem, however. We do a fair amount of Python coding >> in our business, but don't have time to constantly dig through the >> source code of every tool we use. It seems quite difficult to get up >> to speed on all of the capabilities of leo. > > Hmm. My intention is that it should *not* be necessary to understand > all the intricacies of Leo in order to be able to use it. There are > many features of Leo that I use seldom, if ever.
I read, and sympathized with, the comment as seeking answers to questions like: - how do I get a list of children of this node? - how do I generate this subtree of data? - how do I get the filename that this @auto tree represents? - how do I place focus on the node with <this> headline? - ... As a long time Leo user and scripter, I still burn up time answering these. I should study the organization of existing doc, maybe it's optimal, but I think a well organized recipe book would be grand. > > This reminds me about the most important Aha I ever had about Emacs, > namely that one does not have to pay attention to all of Emacs's alt-x > commands in order to use Emacs effectively. The situation is similar, > I think, because I modeled Leo's minibuffer of the Emacs minibuffer > (and all the Emacs alt-x commands). > > True, there has been a lot of development on Leo over the past several > years, but my own work flow has remained almost completely unchanged. > For me, the biggest improvement has been the qttabs gui. At first I > was unimpressed; now, I don't know how I ever lived without it. > >> Even by frequent, careful >> reading of the online help and a couple of years of everyday work with >> leo, we come away feeling like there is so much more there that we >> can't readily access. We monitor these forums and occasionally post >> questions and comments, but it feels like to really have an awareness >> of leo's feature set, you have to spend significant time reading the >> code and understanding it and continuously keep track of this forum. > > To repeat, you should absolutely feel free to ignore the vast majority > of Leo's features, as long as you have a work flow that suites you. > >> Much of capability discussions on this forum address really >> interesting items which don't seem to be addressed in documentation >> anywhere. This leaves the moderately technical to pure users wanting. > > What you are really seeing, I think, is that this forum mostly gets > developer-level discussions. There is a separate help forum, but it > has low traffic. > >> It would be fantastic if all the great things about leo could be >> documented thoroughly so that potential new users could readily >> "access" these capabilities. It seems that the code and features >> within leo develop pretty rapidly, but much of it gets left >> undocumented. > > It's documented in the what's new section: > http://webpages.charter.net/edreamleo/what-is-new.html > > But your point is well taken. There may well be important features > that aren't very well documented. > > Feel free to file bug reports about such sections, or just ask about > them here: I typically use my responses here as pre-writing for more > documentation. > >> The only 'documentation' seems to be snippets of >> discussion threads on this forum. Much of the documentation is >> probably adequate for professional computer scientists, but leaves a >> significant gap for people like me (an engineer who uses code to get >> other work done). Thus, it seems that each time I want to explore a >> new feature of leo, I spend a bunch of time in trial and error trying >> to figure out how it works. > > This could be an opportunity for us both. When this happens again, > please do ask question here, and remind me of this conversation. That > way you can get your answers more quickly, and I will be encouraged to > add the missing documentation. > > I thinks this is the only real way to improve the documentation. It > can't be done in general; it can only be done step by specific step. > > Edward > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To post to this group, send email to leo-editor@googlegroups.com. > To unsubscribe from this group, send email to > leo-editor+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/leo-editor?hl=en. > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
