From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: GUIs (was Re: A comment on Slashdot)
Date: Fri, 14 Apr 2000 20:35:55 -0700 [thread overview]
Message-ID: <005a01bfa68b$c5d81180$70105b80@wang> (raw)
In-Reply-To: <Pine.LNX.4.10.10004122053010.1265-100000@rocky>
Actually, WIndows2000 has MSAA as a part of the operating system. It is not
a question of Microsoft not including their own technology, but who supports
it. However much we blame Microsoft, but at least they are trying to do
something. Many apraised companies like Netscape, didn't even consider
supporting MSAA.
regards,
Vic
----- Original Message -----
From: <cpt.kirk@1tree.net>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, April 12, 2000 7:01 PM
Subject: Re: GUIs (was Re: A comment on Slashdot)
> Here is my take on the issue (for what it is worth). Active Accessibility
> should be a real part of the OS. It should not be a patched version and
> there should not be a special update (except perhaps that if it is updated
> it could be offered until such time as the next core update comes out).
> Basically, if one has the latest updates to the system, they should have
> the latest updates for this.
>
> But to do this would take far more then the small staff they have
> "dedicated" to the task. Instead it would take sitting down and figuring
> out how things work and planning accordingly. I am not a believer. I don't
> believe that there will be a single core for "home" and "business." The
> end of the seperate lines for 95 and NT is always pushed back. That is
> because neither can be modified easily for the intended use. A full
> install of linux OS and X windows is less then half the number of lines of
> code that Win2000 has.
>
> I don't think that the M$ solution will ever be anything else then a
> catch-up for those looking to make it accessible. The only way that would
> change is for the blind people to create the powerful force that the deaf
> people have. Even then, I just don't know. Weasle Bill would probably talk
> about how they couldn't innovate (attempt to turn other people's ideas
> into their private proprietary standard).
>
> Kirk Wood
> Cpt.Kirk@1tree.net
> ------------------
>
> Why can't you be a non-conformist, like everybody else?
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
A comment on Slashdot that concerns me Martin G. McCormick
` GUIs (was Re: A comment on Slashdot) cpt.kirk
` Janina Sajka
` cpt.kirk
` Mike Gorse
` cpt.kirk
` Janina Sajka
` cpt.kirk
` Scott Howell
` Janina Sajka
` cpt.kirk
` Victor Tsaran [this message]
` cpt.kirk
` Victor Tsaran
` cpt.kirk
` Matthew Campbell
` Janina Sajka
` A comment on Slashdot that concerns me Tommy Moore
GUIs (was Re: A comment on Slashdot) Martin G. McCormick
` Christopher Moore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005a01bfa68b$c5d81180$70105b80@wang' \
--to=vtsaran@nimbus.ocis.temple.edu \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).