On Oct 14, 11:33 am, "Edward K. Ream" <[email protected]> wrote: > On Oct 13, 10:43 am, "Edward K. Ream" <[email protected]> wrote:
The first draft of the step-by-step introduction is now complete. Separating the writing from the "shooting" of screenshots and post- production work reduced "dithering" to a minimum. This is probably the best introduction to Leo's basics that has ever been done. I am considering another post-production phase, namely replacing *all* of Leo's tutorial with one or more **single-page slideshows**. These would have the same content as stand-alone slideshows, but the "slides" would be shown one after the other in a single html page. There would be some advantages to such **slideshow pages**: they reduce the "cruft" of navigating between slides, and they reduce the overall page count in Leo's Users Guide. Happily, we can do the slides both ways: as a sequence of individual slides or as one (big!) web page. The is no difference in content at all: the difference is a matter solely of post-production builds. A simple script would create a single rST source page containing the text of all @slide nodes and references (.. image:: directives) to the screenshots. In other words, it will be easy to experiment with single-page slideshows. Edward P.S. The question now becomes, when should the "shoot" begin. That is, when is the screenplay settled enough to justify the substantial expense of actually creating slides with Wink? We don't want to start too soon, because that would result in a lot of needless work. OTOH, we don't want to delay the project by being too timid. Scripts provides the answer. If the meld script is flexible enough, it will be straightforward to add or delete slides in a "Wink" folder, and then to copy the slides to the leo/doc/html/slides folder, renamed to be compatible with the .. image:: references in the @slide nodes created by the make-slide or make-slide-show commands. The scenario for "patching" a slideshow then becomes the following: 1. Regenerate the slideshow. This involves updating .. image references and other pointers in the @slideshow tree. Yet another script may be helpful here. 2. Run the meld script. This will first check that the number of @slide nodes "matches" the number of screenshots. If it does, it will copy files. If not it will issue a warning. Obviously, we want to minimize the number of patches, but with the proper tools (scripts) patching should not be traumatic. This is an important conclusion: it means we can "re-shoot" later without too much trouble. 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.
