On Fri, Aug 20, 2010 at 9:30 AM, Ville M. Vainio <[email protected]> wrote:
>> I'd like to see how much can be done without changing anything in s5.
>> If we need more, we can always add it later.
>
> It's usually a good idea to try using a tool before fixing it :-).
Haha. Well, I've just created my first slideshow from an @rst tree
using the rst3 command.
1. I put the following options in an @ @rst-options doc part in the
root @rst node::
call_docutils=False
write_intermediate_file = True
2. The @rst node defined a title as always::
########
My Slides
########
This became the title of each slide in the slideshow.
3. Each direct child of the @rst node defined a slide. As
recommended, none of the slide nodes had children: they would become
part of the parent slide.
4. Running Leo's rst3 command on @rst slides.html created slides.html.txt.
5. Using a one-line script, I then ran rst2s5 on slides.html.txt to
create slides.s5.html. Voila, a slideshow!
Thus, Leo's present rst3 command is already good for creating slides!
Adding an s5 command would simplify this workflow in several ways:
- No need to override default settings: the s5 command would set
better defaults.
- No need to run a separate script: the s5 command would invoke
Lib\Tools\rst2s5 automatically on the intermediate file.
- The s5 command might optionally warn if slide nodes had children.
These would be nice features to have, and I'll probably add them soon,
but they are in no way essential.
Still to do: organize several slideshows into a toc. Obviously, this
is possible using standard docutils/sphinx mechanisms. I'm not sure
which way would be the most convenient, and whether an s5 command
might create a toc for outlines automatically.
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.
