Larry,
Point well taken. I believe Window-Eyes itself is already quite stable,
and users of scripts should take care when installing something new.
Script Central allows everybody to rate and comment on scripts. This
combined with version numbers, E.G. 0.1, 0.2, etc, should be enough
information to let the user decide whether or not the script is stable
and mature enough to run.
I only use a small selection of global scripts at work since, as you
have discovered, some scripts are more tested and robust than others. I
don't think a script beta team would solve much in the end, though. It
is up to the script author to write their code carefully and completely,
and he/she must keep an open dialogue with users to identify and fix
problems. Similarly, users must examine all of the available facts when
they choose to run something new.
Best regards,
Steve
Larry Naessens wrote:
Steve, I don't think anyone is attempting to criticize you or to call
into question anyone's dedication when it comes to the work that you
put into scripts. I think that part of the dilemma may be that there
are some people here who simply don't know where the problem lives.
Too often for my liking the answer seems to be to request that the
purchaser of the program put in more of their own time in order to
diagnose the problem and sometimes that just isn't practical. I've
always believed that was what beta cycles were about. And, speaking
just for me, I can't conduct business using a screen reader that might
turn renegade on me because I've chosen to load a given script. To
me, and speaking strictly for me, that turns Window-Eyes into a beta.
Rock solid unless you happen to load the wrong script. Does that
really reflect a rock solid philosophy?
So, do I have any suggestions? Sure I do. They may be far from
perfect, but they might be worthy of a look. How about this one? Would
it be possible for scripts to be tested by a group of willing and
interested volunteers before they are released for general
consumption? Certainly Window-Eyes itself goes through that process as
does most software. So, why not scripts?
I guess this would be an unpopular choice for those who want to latch
onto the latest and greatest yesterday if not sooner, but what I need
is a screen reader that can be depended upon to be ready to perform on
a daily basis with a minimum of issues. The $300 charge for an SMA
entitles me to that quality level and nothing less.
Right now, I, personally, speaking strictly for me, see too many
scripts that cause issues in all of my machines. Not just the odd
rebel PC. That, Steve, is why I am likely to load fewer rather than
more scripts onto any of my systems. I simply believe that there must
be a minimum standard and that it must be observed universally before
any script can be released to the public. If that means fewer but more
reliable scripts, I'm ok with that. And please don't tell me that the
current system works for everyone else. I've seen too many concerns
expressed here to buy into that theory. Why not fine tune the
acceptance of scripts prior to public release, so that more of us can
join in on the applause for this
version of Window-eyes?
Larry
Larry Naessens
Vinyl Trans4mations
A Division of Jalana Enterprises
Bradford, Ontario
Phone: 905 918 0658
Vinyl Trans4mations, a Burn Above the Rest
At Vinyl Trans4mations, we turn old records and tapes into brand new
CDs that you can listen to for a lifetime. Visit us at
www.vinylguycafe.com. We welcome all of your enquiries by phone or
email. Before sending us your media, please contact us for important
shipping instructions.
----- Original Message ----- From: "Stephen Clower"
<[EMAIL PROTECTED]>
To: "gw-info-gwmicro.com" <[email protected]>
Sent: Monday, December 01, 2008 3:05 PM
Subject: Re: Scripts, a Mixed blessing?
Stephen Clark wrote:
Same here. I just uninstall all the scripts and everythings fine.
With scripts running I find that WE is extremely unstable which is
very unfortunate. You're not the only one. IMHO, scripts are a
joke and add nothing but instability to an otherwise stable product.
It is unfortunate you believe this to be true. Admittedly, the
scripting engine, if not used correctly, can cause Window-Eyes to act
strangely or crash altogether. However, I and other script developers
do what we can to address all reported issues to ensure our addons
work as seemlessly as possible. If we knew which scripts you had
tried to run along with their version numbers, it would be easier for
all interested parties to get to the bottom of your instability problem.
I have found a few scripts that can cause problems, and I removed
them from now. However, I have 24 loaded into memory that don't slow
Window-Eyes down one bit. This includes the latest copies of the GW
Micro factory scripts and other utilities I've found to be useful.
Bottom line: the more info you provide, the easier it will be to
solve the problem.
Best regards,
Steve
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.
All GW-Info messages are archived at http://www.gwmicro.com/gwinfo,
and can be searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body of the
message.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.
All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be
searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.
