> > Leo is almost tragic in how powerful it is, and how much its adoption is >> held back by poor documentation. Good documentation will be a major >> endeavour, but well worth it. >> > [...] > Newbies only need to know how to search outlines, and which outlines to > search, especially LeoDocs.leo, leoSettings.leo and CheatSheet.leo. > Really, how hard is it to scan the top-level nodes in leoSettings.leo? >
I think this speaks to the mode of learning with a browser open on one side pointed at the docs (and google and forums and stack overflow and ...) and the program-to-learn-about on the other side, experimenting and trying out the things being read about in the browser. Things which don't have browser-discoverable things to read are harder to learn using this common pattern. Two Leo instances can be open side by side but then one is navigating "is there another Leo session open?" warnings and messing about with resizing / dismissing panels to maximize real estate of the reference reading material. It works but has more friction. Here's a comparison: Python has built in help available in any interactive session, but it's easier to use a reference page <https://docs.python.org/3/library/os.path.html> than print it inline with the code and then losing track of the previous command: Matt -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
