Hello Jamal, As a busy user, I just want the list of commands and the summarized documentation first, followed by the more conceptual, longer form documentation in cases where the application is complex enough to need the additional background information. Even in that case, the conceptual info is required only once or twice, even though I may still need to refer to the list of commands for quite sometime. :-)
I'm not asking for extreme detail; just a quick bulleted list specifying those features that have been added and changes made. ----- Original Message ----- From: "Jamal Mazrui" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, September 08, 2008 12:01 PM Subject: Re: Updated packages WinAmp is a complex script with many features, so someone would not want to re-read documentation to find out about changes. I see how the release notes are appreciated, though for me, I wish more documentation was devoted to a conceptual overview of the script features, particularly because WinAmp is quite an unconventional app that is not easy to understand. <grin> Jamal On Mon, 8 Sep 2008, Jeff Bishop wrote: > Date: Mon, 8 Sep 2008 11:47:29 -0700 > From: Jeff Bishop <[EMAIL PROTECTED]> > Reply-To: [email protected] > To: [email protected] > Subject: Re: Updated packages > > Trust me, I released one update without release notes and boy did I hear > about it <grin>. > > Jeff > > ----- Original Message ----- > From: "Aaron Smith" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Monday, September 08, 2008 11:45 AM > Subject: Re: Updated packages > > > > Another thing to remember is that it's quite possible (and probable) > > that > > users of scripts will not be subscribed to this list, or any other list. > > Including a description of what has changed between versions seems > > somewhat important. If you'd rather host your change log somewhere else, > > then simply point that out in your release notes. Keeping people > > informed > > is essential to maintaining a strong and committed user base. > > > > Aaron > > > > Darrell Shandrow wrote: > >> Hello Jamal, > >> > >> Thanks for adding the spelling functionality to the query script. > >> > >> I would like to ask respectfully that you include some sort of change > >> log > >> or release notes in Script Central and in the package whenever you > >> release even a minor update to one of your scripts. Jeff Bishop's > >> Winamp > >> scripts represent just one excellent example of this excellent > >> practice. > >> > >> Thanks, > >> > >> Darrell > >> > >> ----- Original Message ----- > >> From: "Jamal Mazrui" <[EMAIL PROTECTED]> > >> To: <[email protected]> > >> Sent: Monday, September 08, 2008 10:35 AM > >> Subject: Updated packages > >> > >> > >> FYI -- The updates to my packages over the past week have been to > >> implement the best practices incorporated in my latest Script Template. > >> That script, ScriptTemplate.vbs, was reviewed by GW Micro staff to help > >> ensure that shared objects, such as those in GW Toolkit and Homer > >> Shared > >> Object, are being handled in an optimal manner. Responsibility for the > >> code still rests with me, however, so do report any problems you > >> encounter. > >> > >> In general, I announce updates to my packages on this list, including > >> what's new in them. If you discover that a package has been updated > >> but > >> no announcement was made, you can assume that it is a maintenance (bug > >> fix) release without new functionality. I monitor this list and try to > >> fix any bugs reported, as well as add features suggested when possible. > >> Since many of my scripts make use of the library of convenience > >> functions > >> in Homer Shared Object, it is best to install an update to that when > >> available. > >> > >> Version 3.7 of Homer Shared Object fixes a bug that was affecting the > >> Lookup Term script. Version 1.1 of Loaded Scripts says the status > >> categories in a more concise manner. Version 1.1 of Query Setting > >> spells > >> each file name after speaking it. > >> > >> Jamal > >> > > > > -- > > To insure that you receive proper support, please include all past > > correspondence (where applicable), and any relevant information > > pertinent to your situation when submitting a problem report to the GW > > Micro Technical Support Team. > > > > Aaron Smith > > GW Micro > > Phone: 260/489-3671 > > Fax: 260/489-2608 > > WWW: http://www.gwmicro.com > > FTP: ftp://ftp.gwmicro.com > > Technical Support & Web Development > > >
