On Aug 22, 5:31 pm, "Edward K. Ream" <[email protected]> wrote:
> It's a bit off-putting to have one slideshow merge directly into the > next. I doubt that can be fixed easily. Another problem is that sphinx gives errors if a page has no title. I'd actually rather not give each slide a separate title. After some experimentation, using the headline of the first slide as the title for all slides in a slideshow seems best. Of course, this will be a preference. But these are nits. I'll now turn my attention to supporting @image child nodes. The reference (in the headline) should be become image:: markup in the slide. That's trivial to do. Here is a cute thought. We often want to create a screen shot of *another* outline, and put the image in *this* outline. We can do this easily. Suppose node N represents the slide. That is, node N a child of some @slides node. Suppose N has a child node N2 called something like @tree. The script that takes the screen shot will do the following: 1. It looks for an @tree node N as a direct child of the present node p. 2. If such a node exists, the script will select N, do a hoist, take the screen shot and do a dehoist! We'll see N's tree in the screen- shot! We can embed the tree to be shown in the node that creates the screen! One of the demo slideshows will show how to create slideshows using these tricks. It will be a good introduction to @button and all the outline-oriented tricks that scripts can use. 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.
