<[email protected]> 于2018年10月11日周四 下午2:06写道:
>
> > Yes, i meet same problems,
> > but the reason is simple:
> > - Leo release so many years, but the core developer always only EKR
> > - so means more and more knowledge for EKR as natural truth, not need 
> > explain
> > - and servicing big document.leo project is not funny and tired... v
>
> Now that I think about it, I think you hit the nail on the head. Edward knows 
> the software and code too well, and so it's hard for him to see it from a new 
> user's perspective. If anyone is up for it, it may be best that a revamped 
> documentation is done by others, with Edward looking over to make sure it's 
> not inaccurate.
>
> My smaller dream was that I become well versed enough in Leo programming that 
> I would then write my own documentation as a series on my site - starting 
> from the basics of scripting to more advanced usage. I wanted to take 
> features I liked in Emacs and port them to Leo and show how it's done - 
> mostly because I really think many, many programmers out there would use Leo 
> if they only knew how to. People learn a fairly foreign language (Emacs Lisp) 
> to customize their editor. Many more would rather just do it in Python. I 
> don't know if I'll ever become knowledgeable enough to get to that point, 
> though.
>

as ur another mail suggest:
 I'm suggesting that there be an Examples directory in the
distribution, where any file in it or a sub directory of it is treated
as such a template.  It would contain live documents for plugins,
workflows, debugging demos, design notes, generic add a language demo,
unit test demo, todo plugin demo, etc.

...

in fact in any tech community, there is one hide rule:
propose by who, make it by who ;-)

just like EKR, not understand literature programming,
so build Leo to make literature programming environment for everyone.

base the document problems, u r so right:
- want EKR writing friendly document for fresh people, is not the good solve
- but start with anlifer uself, is very good:
-- fork Leo repo.
-- append Examples directory
-- start write down all kinds of u feel need demo/doc./test/...

so EKR and other people can work with your fork,
when the Examples sub path, grow enough, Pull-Request back distribution repo.
Bazinga ;-)
you create new age for Leo document.





> --
> 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.



-- 
life is pathetic, go Pythonic! 人生苦短, Python当歌!
俺: http://zoomquiet.io
授: http://creativecommons.org/licenses/by-sa/2.5/cn/
怒: 冗余不做,日子甭过!备份不做,十恶不赦!
KM keep growing environment culture which promoting organization learning!

-- 
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.

Reply via email to