public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas Ward" <slingshooter@valkyrie.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Gnome, gnopernicus, and X-Windows questions
Date: Wed, 18 Sep 2002 17:00:38 -0400	[thread overview]
Message-ID: <00f601c25f56$711f5460$0100a8c0@stargate> (raw)
In-Reply-To: <20020917225302.15062.7560.Mailman@speech.braille.uwo.ca>

Hi, Charley. I'd like to make some drastic corrections on some comments you
made.


Charley said:
  "Why should we have to do all that installing and compiling to
simply get x-windows to talk right?"

My reply:
 Cause, Gnome 2.0, and gnopernicus is under development, and is not to be
used by the general public at this time.
It is not ready for people like you to use, and it is assumed the developers
will be working with it.
That is the reason it is not built, and out there for just anyone to install
and use.

Charley said:
"but it just drives me up a wall to think that we could have funded good
work and gotten it done much more quickly."

my reply:
 Like how? I mean many people are putting time and money into the Gnome 2.0
project which goes beyond Linux and will give access to Unix platforms as
well as Linux.
Without the speech hooks no screen reader could ever hope to read Gnome
applications or the desktop.
Do you think the people on the speakup list are rushing forward to do all
that work for Gnome?

Charley said:
 "If we just bought
the package and had the access in the box, then how much money would we
not have to spend on another conference on how come we are not working?"

My reply:
Well, once Gnome 2.0 and gnopernicus is complete and ready for general usage
every Linux operating system has the choice to include it in there box
distribution. Some like Red Hat, Mandrake, and Suse have already made plans
to do just that as soon as gnopernicus is released to them to be included in
their distributions.
It also is not tied to a hardware ssynth which brings down cost for the end
user, cross platform portibility, and works in a gui environment similar to
MS Windows which in many respects is easier to train former Windows users
in.

Sumerry:
I think you should get all your facts strait before getting on the list, and
ranting and raving about things you don't know what your talking about.
Find out the goals of a group, their plans, and do some research before
crucifying a group for doing pore work when you haven't done zilch to
research it.





       reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020917225302.15062.7560.Mailman@speech.braille.uwo.ca>
 ` Thomas Ward [this message]
   ` Steve Holmes
     ` Charles Crawford
   ` ccrawford
 ` Thomas Ward
     [not found] <20020916195815.6860.27057.Mailman@speech.braille.uwo.ca>
 ` Thomas D. Ward
   ` ccrawford
     ` Ann Parsons
   ` Monty Lilburn
 Monty Lilburn

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='00f601c25f56$711f5460$0100a8c0@stargate' \
    --to=slingshooter@valkyrie.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).