On Sun, Sep 9, 2012 at 10:21 AM, tfer <
tfeth...@aol.com> wrote:
> The people at Next Day Video uploaded a bunch of videos of the talks at this
> year's PyOhio conference, many thanks to them, they do a great job and just
> did this as a service to the python community. The video turned out pretty
> good, although I'm sure my former english teachers would be cringing with
> the amount of "ah's" that crept in during the first part of the
> presentation.
Many thanks for your presentation.
No one knows better than I how difficult it is to present the Leo Aha.
I particularly liked two of your comments. First, that files are the
smallest unit programmers work with. Second, that Leo generates files
from what is, in effect, a template language. Both give, simple,
clear pictures to people. The Leo Aha isn't in the details!
I'm in the midst of many things at present, but you have inspired me
to see if Leo itself might be improved a bit more to show people what
Leo is about. The proper starting point, as in your talk, is likely to
be quickstart.leo.
Hmm. Suppose we could define a slide show as a "trail". Think of a
trail as a series a series of actions. An action is anything that Leo
can do: select a node, a pane, alter text, etc. A create-trail
command, that would follow what we do. The command would place a text
representation of actions into an @trail node.
We activate the recording button, mess around with Leo and then edit
the @trail node. We can then replay the @trail node to see if it does
what we want.
The next-in-trail and prev-in-trail commands would replay the trail
in an @trail node. When giving a talk with Leo the presenter would do
bind keys to these commands and then just hit the next-in-trail key
repeatedly.
The big advantage of this is that it creates a canned experience that
can be replayed during talks, or just videotaped as the basis, say, of
a u-tube video.
In effect, the @trail node creates a dynamic script of what we want to
show Leo doing. The big question is whether it would be easy enough
to create and edit the @trail node. But assuming that we have done
the (possibly large) amount of work required, we are left with a very
useful tools for presenters. Furthermore, it would be easy enough to
tell newbies how to follow a trail. Once started on the trail, the
newbie would be lead onwards to all of Leo's glories :-)
My hope is that this way would be *much* easier than taking and
editing dozens or hundreds of screen shots. Experience shows that
screenshots are way too clumsy.
Edward