About step 4: The ideas I posted on this post<https://groups.google.com/forum/?hl=en&fromgroups=#!topic/leo-editor/nF2lUEUtaUE> would assure step 4, as per you could "record" a "Leo Tutor" showing how you do changes to leo step by step, with no extra effort than normally performing those changes while the Macro recording is on. I know there is much work involved, but since right now Im unemployed I will be learning Leo and pushing towards the objectives outlined in that document. If you happen not to agree with the ideas, I would like (If possible) to have some pointers on how to begin with that, although I dont need them yet since I am still learning how to use Leo :)
Also, is there any collection of useful users Leo files so I can go through them when I finish the tutorial? Thanks! On Wednesday, May 1, 2013 5:01:46 PM UTC+2, Edward K. Ream wrote: > > I'm still reading Getting Things Done, but it's becoming clear that there > are just a few desired outcomes to be accomplished before the next release > of Leo: > > 1. Newbies can install Leo easily. > 2. Newbies can learn Leo's main features easily. > 3. *Good* documentation exists for all important plugins and main features. > 4. Future project leaders (FPL's) know how to change Leo like I do. > - Secondary: FPL's have the same general knowledge about Leo that I do. > > Installation issues have high priority for obvious reasons. If people > can't install Leo they will have a bad first impression :-) This point has > been reinforced by various threads about install topics. > > Points 2 and 3 are the direct result of the Leo sprint. Point 4 may > ensure that Leo outlives me... > > 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.
