Brilliant! A great step forward for anyone who wants to understand the code base and contribute.
I will put in a feature request: 1) fix the qt dimension of readthedocs, 2) index leo on nullege (http://nullege.com) -- it indexes every string in the project-- and finally, one day, 3) do all that is done with readTheDocs and nullege in Leo! Ouf! I don't think the nullege search engine works, but you can do a Google search on any string in the nullege site: "site:nullege.com areaslider" in Google will find the AreaSlider pyjs class. But actually, you can find any piece of code you want and see the code tree and source. This is very useful to see how a given function is being used everywhere in the code base. Thanks for the readTheDocs link. Bill Le lundi 28 octobre 2013 12:37:15 UTC-7, Jacob Peck a écrit : > > On 10/28/2013 3:29 PM, wgw wrote: > > One last thought about this: most projects that are Leo's size have > > api docs. I'm thinking of something like what you will find here: > > http://pyjs.org/api/ or, of course, here > > http://www.gwtproject.org/javadoc/latest/index.html > > > > Really, what will make Leo popular is getting more programmers > > involved. But convenient api documentation is a must for that to happen! > > > > Bill > > > They're a recent addition, but they're up at > http://leo-editor.readthedocs.org/, and they're updated nightly (3am > EST, I think). > > They are broken in some places, but that can't be helped when using > readthedocs' infrastructure. PyQt4 does NOT play with their sphinx > environment very well. > > -->Jake > -- 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.
