I definitely think it's a good idea to have standardised template for each module page. It would make things much easier to read. I agree with Howard about adding a few more sections to it with proxies, types and catalog entries.
There could also be a section at the bottom with external videos/links to tutorials. I'm not quite following you Howard on the plugins list front. Do you mean stick in the version of QS/OS X that the plugin works with, then if they get updated to we can just change e.g. 10.5 to 10.6 etc. On 25 March 2011 10:30, Howard Melman <[email protected]> wrote: > Just some quick thoughts. > > Modules have more than just actions. They have proxies and types and > catalog entries. > > To me, instructions and examples are too similar. Have you seen the Quick > Reference Sheet I did? > http://mysite.verizon.net/hmelman/QSRef.pdf > (listed on http://qsapp.com/wiki/Where_is_everything%3F) > I think it's useful with just a line containing direct object, action, > indirect object (or whatever parlance you want to use) > Still, I think a screen shot showing an example command window would be > great for the wiki. > > One of the hardest parts of writing the manual was in standardizing on > terminology because QS isn't consistent. I recommend using the terminology > I use in the manual. :) > > FYI, a note for the plugins list, instead of saying Current: Yes/No, I > think it would be better to be Known to be current through and give a > version number. That way the list won't get out of date with new releases. > As people know a module works with later releases, the list could be > updated. My guess is that a lot of modules aren't used by many people and > they'll slowly wither. That's fine. Seeing which ones do get updated, gives > a sense of popularity and helps devs figure out where to devote time. > > Howard > > > > On Mar 24, 2011, at 4:57 PM, junk1 wrote: > > > I don't have the skill with QS that most on this board have, but I > > nonetheless thought I'd give this a go. > > > > Before I got started I thought it might beneficial to have a common > > template. I've attached a rough draft of what I was thinking about > > below. It's real rough, and I encourage anyone interested to tear it > > apart. > > > > Let me know your suggestions. > > > > Attachment: > http://sites.google.com/site/junk1temp/files/WikiTemplate0.1.zip > >
