I am now creating slides without knowing exactly how it's all going to
work. It reminds me of the early days of prototyping Leo using M2C.
The present, possibly-soon-to-be-altered outline structure is:
- @thin screen-shots.txt
- @rst html/slides.html
- @slideshow installation
- slide 1
- slide 2
etc.
- @slideshow what is leo
- slide 1
etc.
Notes:
@thin screen-shots.txt puts everything in a .txt files for sharing on
bzr. It works like all other @thin nodes in LeoDocs.leo: it ensures
that leoDocs.leo doesn't change when contents changes.
@rst html/slides.html is the "gateway" page to all the slideshows. We
want a single such page to show up in the main toc. This node will
have introductory remarks, followed (I think) by an interior toc:
. toctree::
:maxdepth: 1
slideshow-installation
slideshow-what-is-leo
etc
As usual, this toctree refers to html files, but the .html suffixes
are omitted.
The "@slideshow installation" node defines a sequence of slides:
slideshow-installation-1.html
slideshow-installation-2.html
etc.
Things get a bit murky here. I am *guessing* that the following
conventions will make sense:
1. The @slideshow node itself defines the first slide. In other
words, I don't think we need yet another intro page, or rather, the
first slide will be the intro.
2. Somehow the create-slides command will enter the name of all the
slides somewhere, probably in a toctree directive at the end the body
text of the @slideshow node itself. We *might* want such a toctree
directive: it suppresses sphinx warnings. But maybe not: it would
clutter the first slide. Only experimentation will tell what is
reasonable.
3. The top-level children of the @slideshow nodes will become
slides. That much, at least, is clear. Let's call such nodes
**slide nodes**. The headlines need *not* start with @slide or
anything like that. It's not clear whether the headline will be
visible anywhere in the slideshow. In Joe Orr's slides, they are
*almost* invisible: they show up only in the thumbnails view!
4. Presumably, each slide node will have a child that is an @image
node that gives the path to a screen shot.
Note: it took me awhile to track down this capability: it (and @html)
are done in the setAllText method in qtGui.py. Obviously, if I have
trouble finding this cool feature, other people are going to have
trouble as well. Both @html and @image could star in their own
slideshows!
To repeat. Some of this is murky. The cool thing is that I can do
most of the work of making slideshows without knowing exactly how it
all going to turn out! And that's exactly what I am doing.
I've already completed the text portion of Joe Orr's "Installation"
slideshow. It has four child nodes, with the same headlines as Joe's
(almost hidden) slide names. I cut and pasted body text from Joe's
slideshow. The body text of each slide node should be rST/sphinx, so I
did a few trivial translations when cutting and pasting body text.
Now all I have to do is create @image nodes for the screen shots.
When all this is done I should be motivated enough to make it all
work :-) If not, I'll continue working on other slideshows. There is
no risk: the only things that might change are:
A. The precise organization of the outline and
B. Exactly what the create-slides command does.
Neither is going to affect the process of creating slideshows in any
way!
In short, we are getting close to making Leo a really cool authoring
environment for slideshows.
Edward
--
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.
