Hey Jamal, Yes, and, the change history provided by those applications is exactly what I would like to see supplied with scripts. The level of detail isn't always high; just provide release notes at a level of detail appropriate for the complexity of the scripts.
----- Original Message ----- From: "Jamal Mazrui" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, September 08, 2008 11:47 AM Subject: Re: Updated packages Hi Darrell, With EdSharp and FileDir, I do maintain a history of changes, as well as announcing what's new with each significant release. Most of the Window-Eyes scripts I've developed are relatively small, modular programs with a couple paragraphs of documentation that is supposed to be easy to digest (Homer Layout, and IE Max are much larger and more complex). I'm trying to better understand the problem you are having. Do you not see my announcements on this list? If an announcement is made about a script that someone is already using, then I would think that he or she would want to read or save it. If it is a script that someone has not tried before, then I would think that reading all its documentation would be desirable. If a bug was reported, and someone finds that it has not been fixed in an update, then I have made it clear that I want to know that. Please understand that each request of a script developer means more time spent on what otherwise might be other work, so if there is a way that a user can get the same information in another way, that is a win-win. Cheers, Jamal On Mon, 8 Sep 2008, Darrell Shandrow wrote: > Date: Mon, 8 Sep 2008 11:21:34 -0700 > From: Darrell Shandrow <[EMAIL PROTECTED]> > Reply-To: [email protected] > To: [email protected] > Subject: Re: Updated packages > > 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 >
