On Oct 11, 9:16 am, "Edward K. Ream" <[email protected]> wrote:
> I have come to think of my self as producer, director, script > writer, production designer, continuity editor and technical director > in what is, in effect, a series of "slow motion" movies :-) I am also the editor and the entire post-production team ;-) I am starting to wonder whether perhaps a large portion of Leo's documentation might be better as slideshows...The good thing about sphinx is that we can complete change the production design during post production without changing slides or screenshots. But this is getting ahead of myself. There still could be big payoffs from *pre*-production work. Indeed, earlier today I took another look at Wink. http://www.debugmode.com/wink/ BTW, I have absolutely no idea why wink doesn't link to better documentation on its own home page. For me, by far the best way to learn Wink was to read the .pdf user guide, but apparently you have to download Wink first! Anyway, it is now possible to compare the Wink way with the screenshot plugin way. Both have significant advantages. Happily, it will be straightforward to integrate Wink with the screenshot plugin. The big advantage of @slide nodes is that they allow a mixture of text and screenshots. That is, you don't have to have text callouts in the screenshots. Also, the final product looks better, and sphinx integrates the slides into the overall documentation. BUT Wink offers huge advantages when taking masses of screenshots. With Wink, I'll simply open Leo, begin taking screenshots with Alt-Pause, and then start doing things in Leo. Wink will automatically take screenshots on every keystroke and/or mouse click. The "huge" advantage is in continuity and simplicity. I wouldn't have to specify, in dozens of @screenshot trees, what the screen should look like. I just do what I want. There is no need for "continuity" editing at all, because the screenshots are naturally related by whatever I am doing. This is way too good to pass up. Note, however, that a script (screenplay) is still essential. In other words, I still wouldn't want to start "winging it". I'll still want to have some notion about what I am intending to convey :-) Otoh, Wink makes it easy to insert and delete screenshots, so as long as there is enough "raw footage" available there won't be any real problem. Shooting new "footage" during post production runs into continuity problems. For example, the log window would likely be hard to duplicate exactly. This just means that it's best to get the proper footage the first time. Actually, even deleting slides can create continuity problems, but a proper script should minimize those problems. Important: wink can "export" the footage (screenshots) to .png files. These won't be named as in screenshot plugin, but a simple script will rename them (and possibly move them). In short, a clear path exists to integrating Wink-related work flow with the screenshot plugin. Expect some cool slideshows as a result. One more thing. Wink can produce flash videos. We don't want to distribute those, because that's not an open format. But that doesn't prevent using those flash shows for true screencasts! Edward P.S. On taking a second look at Wink, I discovered dozens of .svg files in the Wink Callouts and Shapes directories... 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.
