Thanks, junk1. The overview can be anything - I just copied the text from the last page.
The tutorial video has most of the setup in it. Also, examples could go here - I just didn't have time to write any! I think it's better to have all the functionality of the plugin in the table. We don't know the readers level - some might think they know everything but see something new. There's a Pane 3 column, but there's no pane 3 Opera actions(?) Ctrl +enter - any plugin specific actions in there? I'll ger back to you later with more - I'm going to work. Cheers, Phil. On Apr 1, 5:04 am, junk1 <[email protected]> wrote: > Good: > Table (great!) > Preferences section > Extra requirements column > Overview section > > Issues: > No descriptions > No examples > > Don't understand: > What are "Text and URL actions"? > How will different keystrokes be communicated? > ex) ctrl + enter > How will multipanel (term?) commands be communicated? > ex) display a contacts address book field in large type > > I think that the main issues I'm having might have to do with our > respective understandings of the target audience. QS is a geek tool, > so my approach of coming at it from a dummies perspective might not be > what you guys are looking for. > > I've always warmed to the idea of selling benefits rather than > features. That's why I was thinking the "You wanna do this?" "Here's > how to do it" rational would work. I have to admit, that this approach > might be more suited to a tutorial than a wiki though.
