public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Needs educating: Message from Linux (fwd)
Date: Tue, 22 Jan 2002 20:35:22 -0500	[thread overview]
Message-ID: <015d01c1a3ae$63d931e0$0100a8c0@tward> (raw)
In-Reply-To: <01cd01c1a3a9$634bd840$6501a8c0@alex1.va.home.com>

Hi, let me come at this from another angle. In the Windows world a piece of
software is written, and the company then expects the screen reader
manufacturer to modify their screen reader to support their app. Some such
as Microslop include MSAA support to help the screen reader along after the
fact.
In Gnome 2 we want to write the screen reader, and sstandardize all the tool
kits, documentation, and even the sample source code to clearly show someone
how to write an an accessible app, or to upgrade their app so that it works
with Gnopernicus. So rather than making the screen reader work with the app
we want the desktop and apps to work with the screen reader.

----- Original Message -----
From: Amanda Lee <amanda@shellworld.net>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, January 22, 2002 8:00 PM
Subject: Re: Needs educating: Message from Linux (fwd)


> So in broad terms, the features are equivalent to MSAA?  However, there's
a
> cleaner interface than what MSAA provides because of the overal
> standardization of what is already standardized in Linux???
>
>
> Amanda Lee
>
> ----- Original Message -----
> From: "Thomas Ward" <tward@bright.net>
> To: <speakup@braille.uwo.ca>
> Sent: Tuesday, January 22, 2002 7:43 PM
> Subject: Re: Needs educating: Message from Linux (fwd)
>
>
> > Hi. Wo, hold on here!
> >
> > Ok, let me explain what we are doing with Gnome to clarify things.
First,
> > the gtk tool kit, from which Gnome is written in,  is being rewritten so
> > that anyone using the standard controls, widgets, etc will build
> accessible
> > apps from the get go. Gnome has also been upgraded with speech hooks
that
> > will tell the screen reader what is being presented. Finally, Sun will
be
> > introducing something like the Java Access bridge so that Gnopernicus
can
> > handle Java applications under Linux. Does this clear things up?
> >
> > ----- Original Message -----
> > From: Charles Crawford <ccrawford@acb.org>
> > To: <speakup@braille.uwo.ca>
> > Sent: Tuesday, January 22, 2002 2:27 PM
> > Subject: Re: Needs educating: Message from Linux (fwd)
> >
> >
> > >          Thanks.  I understand what you are saying.  Does this mean
that
> > > there would not be a fix for X-Windows like the MSAA in Windows?
Would
> we
> > > need some kind of major off-screen model?
> > >
> > > -- charlie Crawford.
> > >
> > > At 11:09 AM 1/22/02 -0700, you wrote:
> > > >Actually, being familiar with X myself, I'll answer this one.
> > > >
> > > >Xwindows, is a misnomer, in reality, it's just an X server, and
> clients.
> > The
> > > >server draws to the screen, and sends user input to the clients. The
> > clients
> > > >are the applications, the clients are usually on the same machine as
> the
> > > >server, but they don't have to be.
> > > >
> > > >X itself is nothing more than a network protocol for sending graphic
> data
> > to
> > > >an X workstation, the X protocol has no provisions for button, text
> box,
> > or
> > > >any widgets for that matter, it has: line, circle, filled circle,
> > rectangle,
> > > >filled rectangle, pixmap, etc...
> > > >
> > > >X also sends keyboard input and mouse click locations to the
> applications
> > > >that own the windows they occur in.  Beyond that, X's only other
> > capability
> > > >is to send text glyphs (rendered in a given font) back to
applications
> > that
> > > >request them.
> > > >
> > > >As for widgets, and controls, and a nice unified API for writing
> > programs,
> > > >you need a "toolkit library". What's a toolkit library you ask? A
> better
> > > >question might be "what isn't a toolkit library?"
> > > >First of all, there are a lot of toolkit libraries out there, some
are
> > very
> > > >simple (Athena) while some have a full-blown callback API and can be
> > adjusted
> > > >with themes (GTK, GTK+) and some are object-oriented C++ based APIs
> (QT).
> > > >They all basically do the same thing, provide
> > functions/objects/structures to
> > > >the application to draw typical GUI widgets, and send draw requests
to
> > the X
> > > >server. Here's the hairy part, each toolkit has its own look and
feel,
> > has
> > > >its own API, has its own conventions, and basically has its own
> > everything.
> > > >
> > > >There's also the seperate window manager, which is simply another X
> > client
> > > >which registers a few special functions with the X server so it can
get
> > the
> > > >location and owner of each window and add decorations and task
> switching
> > > >behavior. Some (most) window managers do more than this, but they all
> do
> > at
> > > >least this.
> > > >
> > > >Windows, on the other had, has the equivalent of the toolkit library
> and
> > > >window manager built into the kernel (sort of) and most applications
> > either
> > > >use that, or a custom one that is very similar to it.
> > > >
> > > >I'm sure this is incomplete, but I've already been wracking my brain
> for
> > an
> > > >hour over it, so I'll close here, feel free to ask questions or tell
me
> > about
> > > >parts that are unclear.
> > > > >       Good to see you on this list.  I wonder if there are some
> folks
> > > > out there
> > > > > familiar with XWindows to share the kind of navigation that goes
on
> > with
> > > > > it?  I have no idea.  Is it the same icons and rdio buttons and
all
> of
> > > > > tht?  How is it different than windows and how much more easy
would
> > access
> > > > > be to develop in the XWindows environment?  These are important
> > questions
> > > > > to your point I imagine.
> > > > >
> > > >
> > > >_______________________________________________
> > > >Speakup mailing list
> > > >Speakup@braille.uwo.ca
> > > >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



  reply	other threads:[~ UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Needs educateingRE: " Richard Villa
 ` Needs educating: " David Arocho
   ` Thomas Ward
     ` David Arocho
     ` randy turner
 ` Needs educateingRE: " Kirk Wood
   ` Thomas Ward
     ` Charles Hallenbeck
   ` Raul A. Gallegos
     ` Needs educating: " David Arocho
       ` Charles Crawford
         ` David Arocho
           ` Charles Hallenbeck
             ` Amanda Lee
               ` Geoff Shang
                 ` Charles Crawford
             ` Geoff Shang
         ` Jason
           ` Charles Crawford
             ` Kirk Wood
               ` Amanda Lee
                 ` Kirk Wood
                   ` Amanda Lee
                     ` Georgina
                       ` Kirk Wood
                     ` Kirk Wood
             ` Geoff Shang
             ` Georgina
               ` Amanda Lee
                 ` Georgina
                   ` Amanda Lee
             ` Thomas Ward
               ` Amanda Lee
                 ` Thomas Ward [this message]
                   ` Amanda Lee
                     ` Thomas Ward
                       ` Amanda Lee
                 ` Kirk Wood
               ` Charles Crawford
         ` Kirk Wood
       ` Kirk Wood
     ` Needs educateingRE: " Thomas Ward
     ` Georgina
       ` randy turner
 Needs educating: " Gregory Nowak

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='015d01c1a3ae$63d931e0$0100a8c0@tward' \
    --to=tward@bright.net \
    --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).