Hey, as I said two days ago, Im new here, but I am preparing one Leo file which structures how we could make Leo super easy to learn, more interesting for a much wider public to use, and an extremely useful automation and learning tool. I want to structure that really well so its easy to understand, and It will be what I will be working in during the next weeks or months, after of course I study and understand what Leo can do, as per right now im scratching the surface. Cant wait to post that and read your thoughts. The solution for that again has to do with hotkeys and auto-macro recording. Talk soon.
On Wednesday, May 1, 2013 9:04:59 PM UTC+2, Edward K. Ream wrote: > > On Wed, May 1, 2013 at 12:20 PM, Terry Brown <[email protected]<javascript:> > > wrote: > > Haven't looked at it hard enough to evaluate code, but it doesn't seem >> too excessive for what it does. > > > I agree. Code can usually be improved. Your interesting ideas are what > are important. > > Once again, we have a problem: how to make this code available to those > who might benefit from it? More importantly, how to tell others about the > work you have done when we have all forgotten the details of this > conversation. My interim solution is to file this under Leo/To Document, > but that is something of a delaying tactic. > > 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?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
