Shall I update the template example at http://qsapp.com/wiki/Opera_Module, or leave it for now?
On Apr 1, 2:31 pm, Patrick Robertson <[email protected]> wrote: > I'm getting an error when I try to run your template script in Terminal. I'm > running (with and without the 'ruby' at the start) > > "ruby ./plisttemplate.rb -v -p ~/Library/Application\ > Support/Quicksilver/PlugIns -t template.erb -o ./overrides/ > OnePassword.qsplugin" > > and getting the error (I'm using Snow Leopard's pre-installed 'ruby 1.8.7 > (2009-06-12 patchlevel 174) [universal-darwin10.0]' ) > > I'm not a ruby man, so I'm not sure what's up here. > > On 1 April 2011 14:50, Patrick Robertson <[email protected]>wrote: > > > > > Forwarding this so hopefully it's in the right thread... > > > I haven't had a chance to try out the code, but it definitely sounds like a > > good initial template maker. Then we can modify it to add things like > > tutorials and extended descriptions. A lot of the descriptions in the > > plugins are either non-existent or unhelpful. > > > ---------- Forwarded message ---------- > > From: Eric Doughty-Papassideris <[email protected]> > > Date: 1 April 2011 10:06 > > Subject: Re: Digest for [email protected] - 20 > > Messages in 3 Topics > > To: [email protected] > > > Hi, I'm the author of the Opera Module, and what to thank you for your > > interest. > > I think the whole writing wiki pages per plugin is great idea, but we > > need a way to try out solutions on all plugins so we get something > > generic. As has been suggested, the plist has plenty of info that is > > too hard to read today. > > So as to get the ball rolling, I propose the attached system of > > generating templates. I need some helping getting the template right, > > but I thought I'd share what's done so far. I run the following > > command to generate some template for the plugin : ./plisttemplate.rb > > -v -p ~/Library/Application\ Support/Quicksilver/PlugIns -t > > template.erb -o ./overrides/ OnePassword.qsplugin > > I think we should try and formalise the help format, this is as > > productive a way as I know of =) > > > Best Regards, > > Eric Doughty-Papassideris > > > PS: If the attachment doesn't work, I'm a bit new to google groups, I > > uploaded it here:http://s-softs.com/plisttemplate.tgz > > > On 31 March 2011 22:46, <[email protected]> > > wrote: > > > Today's Topic Summary > > > > Group:http://groups.google.com/group/blacktree-quicksilver/topics > > > > QSApp.com/wiki updates/request [5 Updates] > > > stupid interface tricks [1 Update] > > > Play/Pause and other iTunes actions MISSING [14 Updates] > > > > Topic: QSApp.com/wiki updates/request > > > > philostein <[email protected]> Mar 30 11:01PM -0700 ^ > > > > 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. > > > > philostein <[email protected]> Mar 30 11:04PM -0700 ^ > > > > I've taken some 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, walkthroughs, hints and tips here. > > > > I think it'll be easier to see all the info while still being compact. > > > > Let me know if 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. > > > > Rob McBroom <[email protected]> Mar 31 08:35AM -0400 ^ > > > > On Mar 31, 2011, at 2:04 AM, philostein wrote: > > > >> Let me know if 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. > > > > I like it, myself. > > > > I’ll bet we could achieve almost the same result automagically by looking > > at > > > a plug-in’s Info.plist (which I think is in the works) but until then, > > this > > > will be great. > > > > -- > > > Rob McBroom > > > <http://www.skurfer.com/> > > > > Howard Melman <[email protected]> Mar 31 10:33AM -0400 ^ > > > > 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: > > > > junk1 <[email protected]> Mar 31 01:04PM -0700 ^ > > > > 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... > > read more »
