On Sat, Nov 16, 2013 at 7:49 PM, Edward K. Ream <edream...@gmail.com> wrote: > http://www.screencast.com/t/lUv7sgJh [...] > > I may have gone overboard at the end with callouts, but I saw no other way > to make it clear that the searches changed nodes. Still, it's a bit busy; I > acknowledge that.
I suggest explictly (even more than you already have) speaking about the visual changes on the screen as you take action. For example, before hitting Ctrl-F the first time say something like: "Notice the cursor is blinking in the body pane and the Log tab is active in the upper right pane. Hitting Ctrl-F activates the Find Tab and moves the cursor to the minibuffer." Hmm, but after rewatching, that seems like a bad example because your judicious use of callouts in that part of the video already makes everything I've written above very clear and with fewer words. Maybe a better example would be just before hitting enter for the search. Mention that "the node with headline=Example is currently active". After hitting enter, "A match has been found in the node with the headline='spam'. The matching string is highlighted in the body pane". Being explicit in this way makes it harder for a newbie viewer from missing something which otherwise would have been too subtle to notice. Your use of callouts also helps the viewer to notice these subtleties. Or maybe some callouts can make the above less verbose: [callout around the node with headline=Example] and say, "This node is currently active" [Hit Enter] and say "I hit enter to start the search" [callout around the node with headline=spam] and say, "A match has been found in this node" [callout around the highlighted search string] and say, "The matching string is highlighted in the body pane" Just food for thought...maybe that is overkill. Also, some viewers may wonder what happened to the find tab after the search. Saying something like "the find options are no longer visible because the log tab is reactivated after every search" might be useful. And a reason why if there is one. Basically, if something on the screen changes, it might be worth mentioning/explaining. In the string replace portion of the video, I think it would be helpful to mention that the Ctrl-Shift-R/replace-string command doesn't itself do any replacing. It just sets the search and replace strings and performs the find next command. It isn't until the Ctrl+-/replace-then-find command is executed that the string is actually replaced. Brian -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
