Lot's of ideas re slideshows have been swirling in my thoughts
lately. I'm going to summarize them here to attempt to clarify the
situation.
The question is how to use the various tools at hand: Leo itself,
wink, s5, sphinx, docutils, sikuli, etc.
Sikuli: This is easily dismissed, imo. Slides need custom callouts
and other "decorations". Trying to automate this process would be a
huge waste of time.
S5: The idea is good. The implementation flawed, and much too low a
level.
Sphinx: This should be the basis of slideshows, as shown in the
@slideshow button in LeoDocs.leo. However, each slideshow must be
separate from the rest of Leo's documentation. To do this, it will
probably be necessary to create separate sphinx projects for each
slideshow, which will likely entail creating a separate directory for
each slideshow.
Imo, such extra work is well worthwhile. I plan to prototype it
today. It may be that a new @button script can automate the creation
of a new slideshow.
Wink: I'll use wink as a tool for creating callouts. It should be
quite good at that. But Wink "renders" slideshows as Adobe Flash
files. I don't want that: I want real sphinx slides. The user should
control the pace. Furthermore, there is quite a bit of extra work
involved in creating Flash presentations, and I don't think the extra
work is worthwhile.
As I write this, I see that the plan is straightforward:
1. Use @slideshow nodes to create the framework for slideshows. A big
advantage of this approach is that it creates a permanent record of
both the commentary of a slide (in the rST text of the slide node
itself) and the intended contents of the screenshot (in the child
@screenshot-tree trees).
BTW, it's possible to "prototype" large numbers of slides quickly
simply by writing the rST commentary in each slide node. An rST
comment can briefly describe what is to appear on the screen. Later,
that comment can be "fleshed out" by creating the @screenshot-tree
node, and then actually creating the screenshot with @button
screenshot.
2. Use Wink to add callouts and other visual features to slides. This
is likely going to be fairly tedious, but I see no other way.
3. Use Sphinx to create *independent* slideshows. Each slideshow will
have its own directory. Presumably, making the slideshow will be
simply a matter of doing::
cd <slideshow directory>
make html
4. Knit the slideshows into the rest of Leo's documentation by adding
links to them "by hand" in the "slideshow intro" page. This is easily
done, the links are standard rST references.
Edward
P.S. For reference, yesterday I considered using plain @rst trees to
create all-on-one-page "slideshows". Iirc, wink uses this approach.
It's kinda ironic. Anyway, this may be easy to do, but it is not
good for the reader. Scrolling through a huge page loses the intended
visual effect of a slideshow. This option must be rejected.
EKR
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
