Lev Bishop, le Wed 04 Jul 2007 23:54:32 -0400, a écrit :
Is there a way I can investigate this without needing special braille
hardware
Well, there is a virtual braille device, but it can't replace the fast
physical sense of braille dots.
Samuel
--
Unsubscribe info:
On 7/3/07, Samuel Thibault wrote:
Corinna Vinschen, le Tue 03 Jul 2007 09:54:24 +0200, a écrit :
For using local named pipes you don't need winsock anyway, and for
remote connections you should use Cygwin sockets.
And mixing both is quite difficult. Anyhow, I'll only enable cygwin
sockets
On Jul 3 01:32, Samuel Thibault wrote:
Hi,
Samuel Thibault, le Thu 07 Jun 2007 19:59:25 +0800, a écrit :
Phil Betts, le Thu 07 Jun 2007 12:14:33 +0100, a écrit :
Might I suggest a compromise? Create a new Accessibility group in
setup. It would (at least for now) be the first group
Corinna Vinschen, le Tue 03 Jul 2007 09:54:24 +0200, a écrit :
I'm still not happy with the dependency to ws2_32.
It should still go away and I don't see any reason to keep it.
Yes, we did agree on that in the thread. I will also split the package,
into brltty, xbrlapi, libbrlapi,
Hi,
Samuel Thibault, le Thu 07 Jun 2007 19:59:25 +0800, a écrit :
Phil Betts, le Thu 07 Jun 2007 12:14:33 +0100, a écrit :
Might I suggest a compromise? Create a new Accessibility group in
setup. It would (at least for now) be the first group
That would be a fair compromise, yes.
There
Hi,
(I was busy this week)
Christopher Faylor, le Fri 08 Jun 2007 16:10:16 -0400, a écrit :
Cygwin isn't just a bunch of nifty programs clumped together for the
delight and enjoyment of windows users. It's whole purpose in life is
to provide implementations of programs which use the
On 6/16/07, Samuel Thibault wrote:
Hi,
(I was busy this week)
Christopher Faylor, le Fri 08 Jun 2007 16:10:16 -0400, a écrit :
Cygwin isn't just a bunch of nifty programs clumped together for the
delight and enjoyment of windows users. It's whole purpose in life is
to provide
Christopher Faylor, le Thu 07 Jun 2007 15:01:46 -0400, a écrit :
What about unix domain sockets in cygwin? It sounds like you think they
aren't available.
As I already said several times, it must work with non-cygwin
applications as well.
Samuel
--
Unsubscribe info:
On Fri, Jun 08, 2007 at 03:57:20PM +0800, Samuel Thibault wrote:
Christopher Faylor, le Thu 07 Jun 2007 15:01:46 -0400, a ?crit :
What about unix domain sockets in cygwin? It sounds like you think
they aren't available.
As I already said several times, it must work with non-cygwin
applications
Christopher Faylor, le Fri 08 Jun 2007 10:42:49 -0400, a écrit :
On Fri, Jun 08, 2007 at 03:57:20PM +0800, Samuel Thibault wrote:
Christopher Faylor, le Thu 07 Jun 2007 15:01:46 -0400, a ?crit :
What about unix domain sockets in cygwin? It sounds like you think
they aren't available.
As I
Samuel Thibault, le Fri 08 Jun 2007 23:05:19 +0800, a écrit :
I'm a bit tired to re-explain all of this, I've already had to do it on
other lists, it's really boring to go along all these arguments just
once more... But since you really want some details, here are more:
If you want even more
On Fri, Jun 08, 2007 at 11:05:19PM +0800, Samuel Thibault wrote:
Christopher Faylor, le Fri 08 Jun 2007 10:42:49 -0400, a ?crit :
On Fri, Jun 08, 2007 at 03:57:20PM +0800, Samuel Thibault wrote:
Christopher Faylor, le Thu 07 Jun 2007 15:01:46 -0400, a ?crit :
What about unix domain sockets in
Christopher Faylor wrote on Wednesday, June 06, 2007 8:26 PM::
On Wed, Jun 06, 2007 at 02:22:30PM -0500, DePriest, Jason R. wrote:
On 6/6/07, Dave wrote:
Brian Dessent wrote:
Samuel Thibault wrote:
Mmm, because for a blind person this is a very basic package?
Perhaps, but that doesn't
Hi,
Christopher Faylor, le Wed 06 Jun 2007 16:11:11 -0400, a écrit :
On Thu, Jun 07, 2007 at 03:24:45AM +0800, Samuel Thibault wrote:
Brian Dessent, le Wed 06 Jun 2007 02:42:50 -0700, a ?crit :
Yes, setup automatically selects everything in Base for installation,
Ah, I didn't know that, is
Hi,
Phil Betts, le Thu 07 Jun 2007 12:14:33 +0100, a écrit :
Might I suggest a compromise? Create a new Accessibility group in
setup. It would (at least for now) be the first group
That would be a fair compromise, yes.
Samuel
--
Unsubscribe info:
On Thu, Jun 07, 2007 at 07:49:50PM +0800, Samuel Thibault wrote:
Hi,
Christopher Faylor, le Wed 06 Jun 2007 16:11:11 -0400, a ?crit :
On Thu, Jun 07, 2007 at 03:24:45AM +0800, Samuel Thibault wrote:
Brian Dessent, le Wed 06 Jun 2007 02:42:50 -0700, a ?crit :
Yes, setup automatically selects
On 6/7/07, Christopher Faylor wrote:
On Thu, Jun 07, 2007 at 07:49:50PM +0800, Samuel Thibault wrote:
snip
But when talking about communicating with other applications, we need to
use windows interfaces when the linux API doesn't permit it, shouldn't
we?
Only if you can clearly communicate
On Thu, Jun 07, 2007 at 10:04:26AM -0400, Lev Bishop wrote:
On 6/7/07, Christopher Faylor wrote:
On Thu, Jun 07, 2007 at 07:49:50PM +0800, Samuel Thibault wrote:
snip
But when talking about communicating with other applications, we need to
use windows interfaces when the linux API doesn't
Christopher Faylor, le Thu 07 Jun 2007 08:26:42 -0400, a écrit :
On Thu, Jun 07, 2007 at 07:49:50PM +0800, Samuel Thibault wrote:
Christopher Faylor, le Wed 06 Jun 2007 16:11:11 -0400, a ?crit :
On Thu, Jun 07, 2007 at 03:24:45AM +0800, Samuel Thibault wrote:
Brian Dessent, le Wed 06 Jun
On Fri, Jun 08, 2007 at 12:08:59AM +0800, Samuel Thibault wrote:
To the best of my knowledge, there is no unixish way in cygwin
to access these pipes, so we just used CreateNamedPipe().
So don't use named pipes.
As a result, we have a windows handle to deal with. If we used the
cygwin sockets
Christopher Faylor, le Thu 07 Jun 2007 12:37:44 -0400, a écrit :
On Fri, Jun 08, 2007 at 12:08:59AM +0800, Samuel Thibault wrote:
To the best of my knowledge, there is no unixish way in cygwin
to access these pipes, so we just used CreateNamedPipe().
So don't use named pipes.
What instead?
On 6/7/07, Samuel Thibault wrote:
Christopher Faylor, le Thu 07 Jun 2007 12:37:44 -0400, a écrit :
On Fri, Jun 08, 2007 at 12:08:59AM +0800, Samuel Thibault wrote:
To the best of my knowledge, there is no unixish way in cygwin
to access these pipes, so we just used CreateNamedPipe().
So
Lev Bishop, le Thu 07 Jun 2007 13:41:44 -0400, a écrit :
...around 80MByte/sec, which maybe isn't as fast as it could be using
native functionality, but surely brltty doesn't need *that* much
bandwidth for transferring text?
It doesn't need bandwidth, it needs latency.
Samuel
--
Unsubscribe
On 2007-06-08, Samuel Thibault wrote:
Lev Bishop, le Thu 07 Jun 2007 13:41:44 -0400, a écrit :
...around 80MByte/sec, which maybe isn't as fast as it could be using
native functionality, but surely brltty doesn't need *that* much
bandwidth for transferring text?
It doesn't need
On 6/7/07, Samuel Thibault wrote:
Lev Bishop, le Thu 07 Jun 2007 13:41:44 -0400, a écrit :
...around 80MByte/sec, which maybe isn't as fast as it could be using
native functionality, but surely brltty doesn't need *that* much
bandwidth for transferring text?
It doesn't need bandwidth, it
Lev Bishop, le Thu 07 Jun 2007 14:39:17 -0400, a écrit :
On 6/7/07, Samuel Thibault wrote:
Lev Bishop, le Thu 07 Jun 2007 13:41:44 -0400, a écrit :
...around 80MByte/sec, which maybe isn't as fast as it could be using
native functionality, but surely brltty doesn't need *that* much
I forgot to also say: TCP/IP also often pose problem with firewalls, bad
network configuration, etc...
Samuel
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
On Fri, Jun 08, 2007 at 02:46:19AM +0800, Samuel Thibault wrote:
Lev Bishop, le Thu 07 Jun 2007 14:39:17 -0400, a ?crit :
On 6/7/07, Samuel Thibault wrote:
Lev Bishop, le Thu 07 Jun 2007 13:41:44 -0400, a ?crit :
...around 80MByte/sec, which maybe isn't as fast as it could be using
native
On 6/7/07, Samuel Thibault wrote:
Lev Bishop, le Thu 07 Jun 2007 14:39:17 -0400, a écrit :
...about 2ms round-trip. How is this a problem?
This adds up to the screen reader latency, etc.
Really, we tried both, and while tcp/ip was a bit painful, local sockets
were smooth.
Sorry, but I don't
* Samuel Thibault (Wed, 6 Jun 2007 07:08:31 +0800)
Version 3.8 of brltty has been uploaded.
Access software for a blind person using a soft braille terminal.
Brltty is a background process (daemon) providing access to the Windows
Console for a blind person using a refreshable braille
Thorsten Kampe, le Wed 06 Jun 2007 09:33:04 +0100, a écrit :
* Samuel Thibault (Wed, 6 Jun 2007 07:08:31 +0800)
Version 3.8 of brltty has been uploaded.
Access software for a blind person using a soft braille terminal.
Brltty is a background process (daemon) providing access to the
Samuel Thibault wrote:
Mmm, because for a blind person this is a very basic package?
Perhaps, but that doesn't mean that most Cygwin users are blind.
Are packages from the Base category automatically installed?
Yes, setup automatically selects everything in Base for installation,
which by
On Jun 6 02:42, Brian Dessent wrote:
Samuel Thibault wrote:
Mmm, because for a blind person this is a very basic package?
Perhaps, but that doesn't mean that most Cygwin users are blind.
Perhaps, but that doesn't mean that an accessibility package doesn't
make sense in the Base category.
On Wed, Jun 06, 2007 at 12:26:54PM +0200, Corinna Vinschen wrote:
On Jun 6 02:42, Brian Dessent wrote:
Samuel Thibault wrote:
Mmm, because for a blind person this is a very basic package?
Perhaps, but that doesn't mean that most Cygwin users are blind.
Perhaps, but that doesn't mean that
Brian Dessent wrote:
Samuel Thibault wrote:
Mmm, because for a blind person this is a very basic package?
Perhaps, but that doesn't mean that most Cygwin users are blind.
Last I heard, setup.exe was not particularly friendly wrt screen readers
(cf. package selection). Hence the visually
On 6/6/07, Dave wrote:
Brian Dessent wrote:
Samuel Thibault wrote:
Mmm, because for a blind person this is a very basic package?
Perhaps, but that doesn't mean that most Cygwin users are blind.
Last I heard, setup.exe was not particularly friendly wrt screen readers
(cf. package
On Wed, Jun 06, 2007 at 02:22:30PM -0500, DePriest, Jason R. wrote:
On 6/6/07, Dave wrote:
Brian Dessent wrote:
Samuel Thibault wrote:
Mmm, because for a blind person this is a very basic package?
Perhaps, but that doesn't mean that most Cygwin users are blind.
Last I heard, setup.exe
Samuel Thibault, le Thu 07 Jun 2007 03:24:45 +0800, a écrit :
About the linux-utils dependency, it was needed in previous brltty
revisions, but not any more, so I'll drop it.
You may want to update setup.hint from
http://brl.thefreecat.org/brltty/setup.hint
to fix them as soon as now without
Hi,
DePriest, Jason R., le Wed 06 Jun 2007 14:22:30 -0500, a écrit :
It seems that when you trace the requirements of brltty down, you end
up with xorg, perl, and python packages getting installed.
Python dependency is only hard for compile-time. Brltty doesn't itself
use python. Only python
Brian Dessent, le Wed 06 Jun 2007 02:42:50 -0700, a écrit :
Mmm, because for a blind person this is a very basic package?
Perhaps, but that doesn't mean that most Cygwin users are blind.
Indeed, but as pointed out by DaveK2:
Last I heard, setup.exe was not particularly friendly wrt screen
On Thu, Jun 07, 2007 at 03:24:45AM +0800, Samuel Thibault wrote:
Brian Dessent, le Wed 06 Jun 2007 02:42:50 -0700, a ?crit :
Mmm, because for a blind person this is a very basic package?
Perhaps, but that doesn't mean that most Cygwin users are blind.
Indeed, but as pointed out by DaveK2:
Version 3.8 of brltty has been uploaded.
Access software for a blind person using a soft braille terminal.
Brltty is a background process (daemon) providing access to the Windows
Console for a blind person using a refreshable braille display.
If you have questions or comments, please send them
42 matches
Mail list logo
