Happy Holidays Edward! I want to encourage your "Less Said the Better" (TM:-) initiative, in particular. If I understand correctly, you might attempt to take a newbie by the hand to go from zero to "writing" a small but complete python program in five minutes or so? Alternatively you might start by having a new user import a small working python program and then "factor" it in Leo to show the outline ... and then make a few small tweaks before executing the program from within Leo? (Correct me if I have your vision wrong and am merely conflating my wish list with your vision)
Anyway, I think something like that could have a huge payoff. It should allow python programmer wannabes, especially, to completely sample what Leo can provide that other editors/IDEs cannot in just 5-10 minutes. Following a vehicle sales analogy it would be enough of a hands-on real world context so the user would feel comfortable to drive Leo "home" on their own. KISS. AFTER the intro you could invite the newbie to add some changes or further factor the code base on their own...or "come back tomorrow" to learn how to do "fancy" things (like global find, cloning, myriad @ options, etc). Using again the car sales analogy: you want to get the "customer" to drive the car home TODAY; and you don't want them "thinking" overnight nor visiting other car lots first. There are so many editors out there -- but I've not seen another programmer's tree editor to support top down development and code factoring. I think getting potential new users invested very, very rapidly with a small but "good enough to drive home" subset of Leo commands will grab a lot of new programmers and get them off to a solid start before they can get distracted from their own best interest! :-) Know sales basics: get "kids" fully engaged with the new "toy" and get them to use it and own it before intimidating them too much with all the confusing cockpit choices and power of the jet fighter-bomber cockpit they are ACTUALLY purchasing. ;-/ I still don't know how to use Leo to begin developing a python program in the coursera intro python course I am signed up for. The course instructor is encouraging me to just use IDLE "for now" but I would prefer to get started with a better ... habit? Sorry for the redundancy and poor editing of my message. It is 5 AM and my insomnia is running out! On Saturday, December 24, 2016 at 3:16:41 AM UTC-8, Edward K. Ream wrote: > > The last two years have seen @clean and the clone-find commands. Both are > game changers. My *goal *for the new year is create something similar. > > The *strategy *will be to focus on problems that we have learning or > using Leo. Some possibilities: > > > > *Learning about Leo*The Programming with Leo > <http://leoeditor.com/tutorial-programming.html> tutorial must be > rewritten, following the "less said the better" principle. I'll start with > motivating @file and @others. Everything else is details. > > I am considering a series of "Looking over Edward's shoulder" tutorials. > Instead of slideshows or videos, it may be more effective to throw out a > few haiku-like invitations for discovery, following the how to learn Leo > post <https://groups.google.com/forum/#!topic/leo-editor/aafVEBcF9q4>. > Yes, Leo has a gazillion features, but the basics of Leo are simple, and > there aren't many of them. > > *Editing* > > Leo might benefit from a temporary vim mode. This should be easy to do, > and it might be useful in some situations. Leo might also benefit from a > vim-like "dot" command. > > I am having my doubts that a super-duper outline-based diff > <https://groups.google.com/forum/#!topic/leo-editor/ZKP-X2kCc9s> is going > to be useful. The only time I ever use git diff is when creating a checkin > log. Still, I'll investigate a bit further. > > As always, I'll be looking for ways to better integrate Leo with vim, > emacs, jupyter, etc. > > *Testing* > > The TDD advances > <https://groups.google.com/forum/#!topic/leo-editor/UCcBz-BdHII>, have > stimulated further thoughts. More improvements may follow. > > Leo is a uniquely friendly environment for unit testing. For example, one > could imagine a short script that would generate unit tests for all > commands, or all methods in a file or class. > > *Design and checking* > > After spending considerable time writing the make-stub-files > <https://github.com/edreamleo/make-stub-files> script, I have never used > mypy <http://mypy-lang.org/>. I'll probably play around with checking > next year. Programmers have not begun to use big data to validate/improve > their programs... > > *Understanding* > > The biggest payoff may come from enhancing Leo's unique strength, namely > understanding computer programs, or other complex data. Advances in this > arena will be difficult (impossible) to duplicate in other programs. > > That's all for now. All comments welcome. > > 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
