Hi:
I totally agree that we need a centralized script repository because, in my
job, I am sometimes asked if there is a script for this or that application.
For instance, a few weeks ago, a client who is familiar with both JAWS and
Window-eyes called me and asked if either one had a script for a particular
application that he wanted to use. I found the answer for Window-eyes quite
quickly, but I could not even begin to look for a JAWS script, because there
are JAWS scripts in so many different places, some of which I don't know
about.
Kevin Huber
----- Original Message -----
From: "jim grimsby Jr." <[EMAIL PROTECTED]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Monday, September 22, 2008 11:14 PM
Subject: RE: New Direct Text package
The only type of code that you want to prevent from appearing on Scripps
Central is destructive code.
Otherwise we will start having a system like the competitor.
That is, people will start offering scripts on their home pages, versus on
Scripps Central. As soon as that starts to happen. There will no longer be
a
centralized repository for all scripts.
Currently, this system of using a centralized repository is one of window
eyes greatest strength.
Darrell, you are dealing with open source here.
Or if you prefer, free source.
Please note the word free in this context does not mean zero cost. Even
though currently there is no cost for the scripts.
The word free here means freedom.
This means the script author may produce his scripts however he likes.
You the script user are free to use the script as you see fit subject of
course to the user license agreement.
In this case the script author has elected not to use the change log.
This is his choice and his right and we should all respect that.
Also consider this. We are getting these scripts free of charge
note the definition of the word free, now is zero cost.
So who are we to demand anything? We cannot even demand that it works
the only thing that we can do is express our gratitude when it does, and
report the bugs when it does not.
The GW micro scripts are a slightly different situation, but that is
another
story.
So scripters out there keep up the good work and script as you see fit.
Users out there keep the bug reports coming so that the scripters scripts
can get better.
A good author of any program welcomes feedback.
One thing it is important to understand however is you the user have the
right to give feedback.
The author has the right to act on it as he sees fit.
If you are producing a commercial product, and the authors choose not to
act upon user feedback. Then I suspect, the company producing the product
will find its revenue seriously depleted before too long
however, we the free software developers don't have to care whether you
use
our products or not. We are using them. So therefore, we are doing you a
favor we make them available.
Treat it like the favor it is and respectfully make suggestions
do not get bent out of shape when your suggestion is not implemented.
-----Original Message-----
From: Jared Wright [mailto:[EMAIL PROTECTED]
Sent: Monday, September 22, 2008 7:46 PM
To: [email protected]
Subject: Re: New Direct Text package
Darrell Shandrow wrote:
"I'd go so far as to say that a change log or release notes ought to,
somehow, be required by GW Micro in order to post on SC..."
Somehow I think this would only drive people away from SC and thus
neutralize its SC's usefulness as a whole.
JW
