Since I have folks' attention, if we were to plug into HAL, ORCA, or
NVDA, do all of these systems have APIs that we can connect to, either
through some kind of scripting/COM/or some other means?
Andreas Stefik, Ph.D.
Assistant Professor
Department of Computer Science
Southern Illinois University Edwardsville
On Mon, Jan 25, 2010 at 8:09 AM, Andreas Stefik <stefika@xxxxxxxxx
<mailto:stefika@xxxxxxxxx>> wrote:
Southbean?
Do you mean Sodbeans? It's open source under GPL2. It's definitely
free.
Andreas Stefik, Ph.D.
Assistant Professor
Department of Computer Science
Southern Illinois University Edwardsville
On Sun, Jan 24, 2010 at 11:30 PM, black ares
<matematicianu2003@xxxxxxxxxxx
<mailto:matematicianu2003@xxxxxxxxxxx>> wrote:
very, and it is well doing so.
Regarding the eclipse and southbeans if both are free, I can
give a try.
Eclipse is for sure free because I am using it, let see what
southbean will be.
----- Original Message ----- From: "Jared Wright"
<wright.jaredm@xxxxxxxxx <mailto:wright.jaredm@xxxxxxxxx>>
To: <programmingblind@xxxxxxxxxxxxx
<mailto:programmingblind@xxxxxxxxxxxxx>>
Sent: Sunday, January 24, 2010 9:47 PM
Subject: Re: Screen Reader Compatibility
*sigh*
I give up. Your Windows/Linux comparison is very
appropriate. And the original point of this thread was to
simply state that Window Eyes should get the compatibility
treatment for Sodbeans. At this point I don't even care if
that happens, I use Eclipse for Java anyway. And even if
Sodbeans ends up being a better solution, I'm just going
to keep using what I'm used to. Sounf familiar?
Jared
On 1/24/2010 2:27 PM, Ken Perry wrote:
1. Window Eyes has a self-contained Eloquence driver
now that is equal
to JFW's in every way.
Supposedly however when using eloquence and windows 7
in a 64 bit
environment it seems to crash a hell of a lot more
than Jaws.
2. Who cares who had scripting back in 1998? It's now
2010, friend, and
WE took the time to do there's right, and thus you
have a scripting
environment that uses programming languages we already
use rather than
than proprietary garbage, adheres to better common
programming
Doing it right is not always the end all. The fact
that Jaws has been
around a while means more people know how to deal with
it and quickly get
solutions working. I am not saying Jaws is better
because I don't believe
that what I am saying is there are more people drunk
on the wagon than there
are sober in the crowd. You also have to know more
about coding to get
something working with Window-eyes than you do with
Jaws. In fact this
shows when it comes to seeing how many new things are
being done for
Window-eyes verses how many scripts pop up for Jaws on
a regular bases. It
takes a coder to write scripts for window-eyes it
takes a person just
mucking around to get things working for Jaws.
practices, and supports COM automation (which is truly
a beautiful thing.)
Jaws has a way you can use comm. Objects but again I
am not saying it is
great and I am not saying many people use it but I
have played with it
myself back when we started the visual studio scripts.
The only reason we
didn't use more automation in those scripts to start
with is then they would
only work with visual studio pro. Someone should
revisit those scripts and
make a pro only version that would make visual studio
even more accessible.
3. The JAWS SMA authorizes only two upgrades, while
WE's authorizes three.
Oh boy that is a big difference (NOT) when you end up
getting a service like
VA or state services to buy it I don't care how many
upgrades they offer
till they drop the prices to compete against system
access it don't really
matter. System access and NVDA might start forcing
these two FS and GW to
drop their prices in the near future but for now they
are pretty much the
same.
4. JAWS requires an additional $200 for remote desktop
access. Window
Eyes does not, making the pricing difference even more
clear.
This is only something those of us in the high tech
fields really care
about. Normal working people still go with Jaws
because the first part in
this list a work application can be quickly made
accessible with no compiler
and no major knowledge of programming.
5. If you insist on cracking, Window Eyes is an easier
crack than JFW.
Um yeah now there is a good thing to say. Yes my
software is better because
it can be hacked in fact the way they did their
scripting language has made
it really hackible you can even put viruses in other
peoples computers while
you're writing your scripts for window-eyes that's
good news.
Look it's not worth fighting over which screen reader
is better. You can
say Linux is better but right now Windows is the
dominate OS and probably
will be for some time. Of course it's only the more
dominate when you look
at desk tops. Window-eyes is doing some good things
in the way they are
marketing to some schools but System access has them
beat free is always
better than cheap. I think the entire access field is
about to be stud on
its head because we are changing from a desktop world
to a pocket world and
Things are becoming more accessible out of the box
which makes system access
and voice over and others like that a better solution.
There is no reason
to have a scripting language at all in the long run
you just script the OS
and make whatever screen read you want talk. I think
we will find a whole
new world in 2 years at the most.
Ken
__________
View the list's information and change your settings at
http://www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
http://www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
http://www.freelists.org/list/programmingblind