From: Ryan Mann <rmann@rmisp.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Lindows preview.
Date: Tue, 27 Nov 2001 15:45:45 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.33.0111271543460.12620-100000@rmnet> (raw)
In-Reply-To: <01112710102100.19715@lightstar>
That may be true, but Lindows claims to be able to run Windows
aplications. I would think that since Jaws is a windows aplication, it
would work like any other. Maybe it's just wishful thinking on my part.
On Tue, 27 Nov 2001, Jason wrote:
> OK, here's the deal on "lindows"
> It uses "Wine", a "Windows compatability layer" for linux. Wine requires X.
> My best guess is that JAWS for windows won't run under Wine. I don't have a
> copy to test with myself, but knowing what I do about the way Wine seperates
> programs from each other quite a bit more than Windows does I doubt the
> needed "common ground" that JAWS depends on would be present.
>
> Oh yeah, as an aside, the version of Wine that lindows will ship with is
> modified slightly; it contains significantly better support for DirectX and
> OpenGL than the regular version of Wine.
>
> On a completely unrelated note, it could be possible to write a version of
> Wine that doesn't use X and simply dumps text to a console for speakup, or
> whatever else, to read. No, I'm not volunteering for that project :-P
> But if anytone happens to want to start a project to hack X and the relevent
> toolkit libraries into accessible submission, I'll join, I've even got the
> beginnings of a structure worked out for all of it.
>
> (hmmm.... this e-mail got a lot longer than I intended)
>
> On Tuesday November 27, 2001 02:35 am, you wrote:
> > the same question occurred to me too.
> > but it also occurred to me that if lindows is able to run both linux and
> > windows programs as suggested, would you not be able to run your
> > existing windows screen reader as well as speakup?
> > of course not at the same time <evil grin>
> > I thought that the idea of lindows was to have a thin translation layer
> > for interpreting windows stuff.
> > at least that's what I remember from what I've seen about it anyway.
> > On
>
> _______________________________________________
> 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: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Thomas Ward
` Guy Schlosser
` Tommy Moore
` Thomas Ward
` Shaun Oliver
` Jason
` Ryan Mann [this message]
` Thomas Ward
` Saqib Shaikh
` Gregory Nowak
` David Poehlman
` Charles Hallenbeck
Dawes, Stephen
` Tommy Moore
Dawes, Stephen
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=Pine.LNX.4.33.0111271543460.12620-100000@rmnet \
--to=rmann@rmisp.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).