Hi Peter:
A majority of sighted people don't know programming, or want to. So why
should it be different for blind people. I
----- Original Message -----
From: "Peter Wolfe" <[email protected]>
To: "Kevin Simon Huber" <[email protected]>
Sent: Tuesday, July 07, 2009 10:32 AM
Subject: Re: WE Vrs. JFW
The uglyness is that so many blind people don't even know proraming
that it's not even funny. The ones that do monopolize on it that can
easily be seen on this list and that of the internet as an whole. The
truth is that scripting is done by lots of sighted people that don't
care if us blind people get anywhere. What has changed in ten years?
Much of nothing overall just more technology that we can't afford
because we are not employed, under paid, neglected, and shows the
ignorance and arrogance of the american people.
On 7/7/09, Kevin Simon Huber <[email protected]> wrote:
Hi Jim:
O yes, Window-eyes could definitely use more application scripts, and the
beauty of it is, that since Window-eyes scripts can be written in any one
of
several standard languages, there is more potential for scripters to come
forward and write some of those scripts.
Kevin Huber
----- Original Message -----
From: "Jim Grimsby JR." <[email protected]>
To: "'Kevin Huber'" <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, July 07, 2009 8:03 AM
Subject: RE: WE Vrs. JFW
You can but it is not very easy for users to add global scripts. With
window-eyes it is so much easier to add them. now again I must agree
with
Jamie though window-eyes needs a lot more application scripts.
I am hoping over the summer when I don't have kids here every day to start
really getting to work on window-eyes scripting. You know how it is
things
have a way of happening.
☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺☺ Jim Grimsby Junior.
Please feel free to contact me at anytime using one of the below methods.
Skype: Jim.Grimsby 909-498-4711.
E-mail: [email protected]
Windows live messenger: [email protected]
-----Original Message-----
From: Kevin Huber [mailto:[email protected]]
Sent: Monday, July 06, 2009 11:11 AM
To: gw-info
Subject: Re: WE Vrs. JFW
Hi Jamie:
I would like to point out that, although a number of Window-eyes
scripts which are available are not application scripts, many of them
just add features to Window-eyes which are not available in its core.
The Virtual View script and the Autocomplete scripts are perfect
examples of this. I would therefore argue that many of the scripts
which are not application scripts are very useful.
As a matter of fact, I don't know if you can add features to JAWS by
writing a script.
Kevin Huber
On 7/6/09, Jamie Pauls <[email protected]> wrote:
Chip, I would like to thank you and others like yourself who are writing
WE
scripts that help all of us so much. There are a few examples of stellar
Jaws scripts, but not a lot. I really believe that only when some really
useful scripts are written for WE will the blind community in general
start
to take notice. I realize that many of the scripts on Script Central are
proof of concept scripts, and that these are very important in their own
right, but I for one look forward to the WE iTunes script that gives
jTunes
a real run for its money. That's just an example, but I truly would use
such
a script.
----- Original Message -----
From: "Chip Orange" <[email protected]>
To: <[email protected]>
Sent: Sunday, July 05, 2009 8:42 PM
Subject: RE: WE Vrs. JFW
Hi Edward,
speaking of Word support, I just released the version of the MS Word
script
which fixes the bug where WE mis-reports the font size as you change it
via
a command key.
Are there any other Word issues which still need attention?
Speaking of this, I can't emphasize how important it is to have the
ability
to address these types of issues in your screen reader. I also can't
get
across how difficult I found it, when I tried to do anything like this
in
the jaws scripting environment, and how relatively easy it is in WE, and
how
much support I receive from WE (both their support people and their
developers) for each and every one of my scripting projects. Perhaps I
found jaws so difficult simply because I had no such support, at all,
from
the FS folks.
I want to write scripts for myself of course, which I personally find
interesting, but I write them for projects such as Word in part, to help
GW
and help return something for all that free support I've received from
them
as I've learned scripting. Jay McCarty's script which gives java
support
to
WE is the ultimate example of what's possible here in having scripts
dramatically increase accessibility. It's not that FS couldn't do
something
similar, but I think few jaws users could.
Chip
-----Original Message-----
From: Edward Marquette [mailto:[email protected]]
Sent: Sunday, July 05, 2009 7:43 PM
To: [email protected]
Subject: WE Vrs. JFW
Everyone is probably tired of this by now, but the comment about
technical
support at WE was nothing short of astounding. When was the last time
anyone saw an FS employee on a listserv helping users? I never, ever,
ever
saw that. Yet, GW Micro employees, like Aaron Smith, are often on this
listserv (and often on weekends and holidays).
I've been through just about all the screen readers. I started with PC
Speak. Most of the listers never even heard of that one. Then, there
was
the PC Talking program. Then, there was Vocal-Eyes, and next Window
Bridge.
I was a faithful Window-Eyes user until 2004, when I had to have support
for
colors, track changes, and many of the editing features in MS Word that
WE
didn't support. I bought JFW, and used it happily until a year ago.
I switched, not necessarily because I wanted to, but because the tech
support people at my firm (more than 800 lawyers) asked me if there were
not
some alternative to JFW. It all centered around remote access through
Citrix. It wasn't that the FS people didn't try; however, afer
escalation
after escalation, the dopy protection scheme just failed, right in the
middle of a remote access session -- proclaiming that my version wasn't
properly authorized. Our tech support people are very good. One worked
at
Citrix.
So, after verifying that WE had the support for MS Word that I needed, I
switched back a year ago, and WOW.
The remote access is incredible. Even our tech support people are
amazed
at
how responsive WE is.
I'm not saying it was a walk in the park to get it working, but compared
to
he headaches we had with JFW, it was a walk in the park.
That's my story.
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.
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.
__________ Information from ESET Smart Security, version of virus
signature
database 4219 (20090705) __________
The message was checked by ESET Smart Security.
http://www.eset.com
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.
--
Peter
Webmaster
http://www.darkstruggle.com
[email protected]
alternative e-mail
[email protected]
__________ Information from ESET Smart Security, version of virus signature
database 4222 (20090707) __________
The message was checked by ESET Smart Security.
http://www.eset.com
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.
