On Tue, Oct 27, 2015 at 10:39 AM, Jacob Peck <[email protected]> wrote:
> On 10/27/2015 11:34 AM, Edward K. Ream wrote: > > Imo, nobody could grok these advantages by reading documentation or > reviews. I just had to immerse myself in the new language. Probably the > same is true about Leo programming. > > I just have to say that this is perhaps the single most salient line in > this entire thread as far as new users are concerned. I am very skeptical > if there *is* a way to make the documentation show what Leo can do and > why people should use it. > > I think that there should be a line somewhere in the docs that state this. > > It should be clear that Leo requires an *investment* of your time to > understand, but that it has the potential for immense *payoff* in the > form of a deeper understanding of data and relations. I think that the > docs should be blunt when it comes to this -- there's nothing wrong with > coddling a new user at first, but unless the docs make it clear that > there's a time to remove training wheels and dive in, I don't know how many > people will ever stick with Leo enough to make it useful to them. > Hey. This is a great idea. I and the other "usual suspects" have forgotten what it was like before we had Leo. In my case, the second Great Aha was that I could use the MORE outliner to prototype Leo. Within an hour of using MORE I saw the need for @others. More details here <http://leoeditor.com/history.html#breakthroughs>. Still, people probably need at least some hints about why it might be worth their while to jump in and make the investment. I'll think about this... Edward -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
