Thanks Darrell. I did temporarily experiment with including them with the wepm, but I found it slightly pointless for my scripts when Script Central already offers a mechanism to have this information relayed at the point of update. Let's face it, us scripting folks do like a shortcut when we see it <grin>.
Darren On 06/09/2008, Darrell Shandrow <[EMAIL PROTECTED]> wrote: > Hello Darren, > > No. The solution that has been implemented by most scripters is great. I'm > just advocating that all scripters do it. :-) Some high profile scripts > don't have release notes of any kind indicating the changes. > > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Saturday, September 06, 2008 8:08 AM > Subject: Re: Updated scripts really should include release notes! > > > Hi Darrell, > > Can you be a little more specific? If you go to the web page for most > scripts, the release notes for each incremental version are listed and > this page is also stripped of all formatting and shown in the edit box > that displays any new information when an update is detected. Are you > advocating inclusion of this same information staticly in the WEPM > file itself? > > Darren > > On 06/09/2008, Darrell Shandrow <[EMAIL PROTECTED]> wrote: >> Hello Everyone, >> >> I feel strongly that any script updated on Script Central ought to include >> release notes providing, at a bare minimum, a short summary of the changes >> made since the previous version was released. >> >> I don't necessarily want to update a piece of software, including a >> Window-Eyes script, simply because it is available. I want to have an idea >> what changes might be made to my Window-Eyes implementation, how those >> changes might impact my use of the application for which the script was >> written, and the new features available in the update. FWIW, this is just >> my >> two cents. :-) >> >> Regards, >> >> >> Darrell Shandrow - Accessibility Evangelist >> Information should be accessible to us without need of translation by >> another person. >> Blind Access Journal blog and podcast: http://www.blindaccessjournal.com > >
