>From http://youtu.be/xYiiD-p2q80 at 12:13:
We want to avoid the tap that turns the wrong way: that leads to confusion, frustration and anger. In general, Leo's outlines are familiar: clicks work as expected, as do arrow keys, which are based on Windows Explorer. Here are the problem areas for Leo: QQQ If you're not going to use an existing convention, you need to be sure that what you're replacing it with either: a) is so clear and self explanatory that there's no learning curve (so it's as good as a convention) or b) adds so much value that it's worth the small learning curve. QQQ You could say that having source files be *nothing but* text is the "existing convention". In this sense, @others and section references are something new. Obviously, point a does not apply. Just as obviously, there is no way I would ever get rid of @others or section references. Indeed, learning how to create text *is* worth the learning curve, but it's really really important to make sure people can indeed create external files. Another applicable quote: QQQ Even when people know they *could* solve a problem or perform a calculation if they put *effort* into it sometimes they *don't do it* because they don't consider the *potential reward* worth the effort. QQQ No doubt some people have given up on Leo because of just this point. Indeed, I suspect many people never even consider using Leo because they don't realize how limited plain text files are. I'm not sure how to deal with this, but the enthusiastic reaction of people who *do* use Leo shows that there is a real difference between the Leonine way and the plain old way ;-) 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/groups/opt_out.
