I mostly like it. The following is longer than I thought to type, but I think it's mostly nits. I think it's important to get the example template right so others can copy it effectively but feel free to say I'm being too picky.
Overview and tutorials are great. The Overview example text could use a little more detail. All plugins "Help Quicksilver interact with" and "Opera" is the name of the module so the only word that provides info is "browser". If you don't know what Opera is, it explains that it's a browser and that is very useful. I'd rather see something like "Support for the Opera browser, including an Open With Opera action and exposing bookmarks and more in the catalog." I somehow feel the link to the author's homepage should be in some template but I'm not sure where (maybe with version number?). I like the information but not necessarily the layout of the giant grids with mostly empty space. I don't understand why having an info button should have the important first spot. The most important thing that plugins add are Actions and Catalog items and I think those should be first in that order. I do like the hierarchy being shown in the catalog and the type for actions but it took me a little to figure it out. Maybe bolding the actions and catalog entries like they are in the Commands section to make them stand out? In commands I don't understand "Items in brackets are additional instructions." I don't see brackets, [], though I do see parenthesis (). And it looks like additional instructions are in the Extra Requirements and Notes columns. I believe Proxy Objects requires Advanced Features to be enabled so that should be listed in requirements and you probably shouldn't start off with something that requires Advanced Features. Also Current Web Page comes from the Safari plugin (which should be in requirements) so while it works, it probably shouldn't be here at all since it's the same as URL. What I'd do in this case is under Operas current web page, in the note I'd say not to be confused with the badly named Current web page proxy object which refers only to Safari's current page. For the Copy from Opera to scripts I think it's useful to list them all on their own line and not just in the note say there are others. I'm guessing there's are copy to Opera variants and currently I don't know their name. Is "Operas open tabs" a proxy object or only available via right-arrow into Opera.app? I assume Opera needs to be running for this so that should be in the notes. I'd think these things should be grouped together and not separated by a proxy object example. Maybe these should be up in the preferences items section but I'm not sure how. I appreciate that saying "(Text and URL actions)" tells you a list of available actions but I think I still want to see specific examples. I'm not sure what I'd do with an open tab other than show or close and these aren't text or URL actions. I assume searches work with Find With... and Search For... which require the Web Searches plugin and probably should be listed explicitly for people to find and need something in the third pane (its listed as blank). Howard On Mar 31, 2011, at 2:01 AM, philostein wrote: > I've taken a lot of junk1's ideas and Patrick's wish to have fewer > screenshots, and come up with this: > http://qsapp.com/wiki/Opera_Module > > There's 4 sections: > > - Overview > - Preference Items > - Commands > - Tutorials > > Some details: > > - Overview: A quick summary of what the plugin does with a interface > window image (75% size jpg 20 kb). > > - Preference Items: What the plugin adds to Preferences. I've bulleted > the navigation structure to hopefully make the items easier to find. > > - Commands: Instead of just Actions, I think it's better to list > Commands. Plugins sometimes add objects (e.g., scripts, Address Book > contacts) and catalog entries as well as actions. There's columns for > extra requirements (e.g., Proxy Objects catalog entry needs to be > checked) and notes. > > - Tutorials: Videos (no bandwidth), walkthroughs, hints and tips here. > > I think it'll be easier to see all the info while still being compact. > > Let me know what you think. If this is a goer, I'll add a template > page to the wiki to make it easier for anyone to add pages. > > Notes: Opera's current web page Proxy is broken in ß58? How to align > text to the top of tables in the wiki? > > Cheers, Phil. > > On Mar 30, 6:45 am, philostein <[email protected]> wrote: >> Perhaps just one image near the top as an example, then a template >> format for other actions. >> >> What about a table with First pane, second pane, third pane columns? >> >> On Mar 30, 6:24 am, Patrick Robertson <[email protected]> >> wrote: >> >> >> >>>> Although I freely admit that I only tested it for about 3 seconds with >> >>> B58. It works great with B54. >> >>> Works beautifully on B58 for me ;) >> >>>> Here's the revision. Let me know what I got wrong. >> >>> Looks good to me. I think it may be good to have a short one liner >>> description at the top of every page (similar to what you see in QS when you >>> click the 'i' but better as these are pretty rubbish) >> >>> Does everyone think images are necessary? They look nice but I'm not sure... >> >>> On 30 March 2011 05:49, Rob McBroom <[email protected]> wrote: >> >>>> On Mar 25, 2011, at 5:54 PM, philostein wrote: >> >>>>> I updated the Calculator and Tatau info. I added the Remote Hosts >>>>> Module - sorry, I must have missed that one somehow. (If you're >>>>> reading Rob, does this work still?) >> >>>> I was out of town - catching up. >> >>>> You mean does the plug-in work? I think it was written after 10.6 was out, >>>> so… yeah. :) >> >>>> Although I freely admit that I only tested it for about 3 seconds with B58. >>>> It works great with B54. >> >>>> -- >>>> Rob McBroom >>>> <http://www.skurfer.com/>
