speakup question

speakup question

[Igor Gueths]

Hi all. Does anyone know why Speakup doesn't use the standard conventions when designing kernel modules? In other words, why are the drivers not modularized? Because my plan at least for the dectalk driver was to write the standard module code, and then dump the rest of the driver-specific code into the new re-written version. I am doing this for two reasons. 1. I want to keep the changes as error free as possible. 2. I don't want to have problems after writing new code. And I think most of the driver is fine the way it is. I have other reasons for modularizing the driver, including a project I am currently working on that requires this. 

speakup question

[John covici]

The problem is that speakup needs to be alive before modules, before
a file system and before much of anything except the console is
around.

I understand Kirk is working on a scheme to allow modules, but if its
a Dectalk pc, it won't talk at boot, but will have to wait till a
file is downloaded into it (at least that is my understanding, I
don't have one of those).

on Sunday 06/16/2002 Igor Gueths(igueths@attbi.com) wrote
 > Hi all. Does anyone know why Speakup doesn't use the standard conventions when designing kernel modules? In other words, why are the drivers not modularized? Because my plan at least for the dectalk driver was to write the standard module code, and then dump the rest of the driver-specific code into the new re-written version. I am doing this for two reasons. 1. I want to keep the changes as error free as possible. 2. I don't want to have problems after writing new code. And I think most of the driver is fine the way it is. I have other reasons for modularizing the driver, including a project I am currently working on that requires this. 
 > 
 > 
 > _______________________________________________
 > Speakup mailing list
 > Speakup@braille.uwo.ca
 > http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
         John Covici
         covici@ccs.covici.com

Re: speakup question

[Igor Gueths]

Hi John. This is all correct, however as far as I know the synthesizer driver is what's up before anything else. It would be nice to have documentation on exactly what Speakup does at boot time i.e., synthesizer driver initialization, etc. This would help me a lot in my development, however such docs don't seem to be available. Looks like I'll have to dig up everything by hand. 
----- Original Message ----- 
From: John covici <covici@ccs.covici.com>
To: <speakup@braille.uwo.ca>
Sent: Sunday, June 16, 2002 9:10 PM
Subject: speakup question


> The problem is that speakup needs to be alive before modules, before
> a file system and before much of anything except the console is
> around.
> 
> I understand Kirk is working on a scheme to allow modules, but if its
> a Dectalk pc, it won't talk at boot, but will have to wait till a
> file is downloaded into it (at least that is my understanding, I
> don't have one of those).
> 
> on Sunday 06/16/2002 Igor Gueths(igueths@attbi.com) wrote
>  > Hi all. Does anyone know why Speakup doesn't use the standard conventions when designing kernel modules? In other words, why are the drivers not modularized? Because my plan at least for the dectalk driver was to write the standard module code, and then dump the rest of the driver-specific code into the new re-written version. I am doing this for two reasons. 1. I want to keep the changes as error free as possible. 2. I don't want to have problems after writing new code. And I think most of the driver is fine the way it is. I have other reasons for modularizing the driver, including a project I am currently working on that requires this. 
>  > 
>  > 
>  > _______________________________________________
>  > Speakup mailing list
>  > Speakup@braille.uwo.ca
>  > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> -- 
>          John Covici
>          covici@ccs.covici.com
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: speakup question

['Georgina']

Hi

I don't understand, you can view the source and for those synthesisers
that are not supported, perhaps you could get the specs and write
drivers yourself.

Have you tried to ask Kirk specific questions?

Gena



Blindness Advocacy and Self Help Online www.bashonline.org

>Hi John. This is all correct, however as far as I know the synthesizer =
>driver is what's up before anything else. It would be nice to have =
>documentation on exactly what Speakup does at boot time i.e., =
>synthesizer driver initialization, etc. This would help me a lot in my =
>development, however such docs don't seem to be available. Looks like =
>I'll have to dig up everything by hand.=20
>----- Original Message -----=20
>From: John covici <covici@ccs.covici.com>
>To: <speakup@braille.uwo.ca>
>Sent: Sunday, June 16, 2002 9:10 PM
>Subject: speakup question
>
>
>> The problem is that speakup needs to be alive before modules, before
>> a file system and before much of anything except the console is
>> around.
>>=20
>> I understand Kirk is working on a scheme to allow modules, but if its
>> a Dectalk pc, it won't talk at boot, but will have to wait till a
>> file is downloaded into it (at least that is my understanding, I
>> don't have one of those).
>>=20
>> on Sunday 06/16/2002 Igor Gueths(igueths@attbi.com) wrote
>>  > Hi all. Does anyone know why Speakup doesn't use the standard =
>conventions when designing kernel modules? In other words, why are the =
>drivers not modularized? Because my plan at least for the dectalk driver =
>was to write the standard module code, and then dump the rest of the =
>driver-specific code into the new re-written version. I am doing this =
>for two reasons. 1. I want to keep the changes as error free as =
>possible. 2. I don't want to have problems after writing new code. And I =
>think most of the driver is fine the way it is. I have other reasons for =
>modularizing the driver, including a project I am currently working on =
>that requires this.=20
>>  >=20
>>  >=20
>>  > _______________________________________________
>>  > Speakup mailing list
>>  > Speakup@braille.uwo.ca
>>  > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>=20
>> --=20
>>          John Covici
>>          covici@ccs.covici.com
>>=20
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>=20
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: speakup question

[Igor Gueths]

Hi. This is true. I just odn't have my box here right now so I can look at the sourcecode. However, what I was looking for was exactly how Speakup initializes itself during the boot process. For example, how is Speakup able to start first in the boot sequence? Are the routines for rs232 communication for external synths defined in speakup.h? 
----- Original Message ----- 
From: 'Georgina' <gena@gena-j.net>
To: <speakup@braille.uwo.ca>
Sent: Monday, June 17, 2002 6:19 AM
Subject: Re: speakup question 


> Hi
> 
> I don't understand, you can view the source and for those synthesisers
> that are not supported, perhaps you could get the specs and write
> drivers yourself.
> 
> Have you tried to ask Kirk specific questions?
> 
> Gena
> 
> 
> 
> Blindness Advocacy and Self Help Online www.bashonline.org
> 
> >Hi John. This is all correct, however as far as I know the synthesizer =
> >driver is what's up before anything else. It would be nice to have =
> >documentation on exactly what Speakup does at boot time i.e., =
> >synthesizer driver initialization, etc. This would help me a lot in my =
> >development, however such docs don't seem to be available. Looks like =
> >I'll have to dig up everything by hand.=20
> >----- Original Message -----=20
> >From: John covici <covici@ccs.covici.com>
> >To: <speakup@braille.uwo.ca>
> >Sent: Sunday, June 16, 2002 9:10 PM
> >Subject: speakup question
> >
> >
> >> The problem is that speakup needs to be alive before modules, before
> >> a file system and before much of anything except the console is
> >> around.
> >>=20
> >> I understand Kirk is working on a scheme to allow modules, but if its
> >> a Dectalk pc, it won't talk at boot, but will have to wait till a
> >> file is downloaded into it (at least that is my understanding, I
> >> don't have one of those).
> >>=20
> >> on Sunday 06/16/2002 Igor Gueths(igueths@attbi.com) wrote
> >>  > Hi all. Does anyone know why Speakup doesn't use the standard =
> >conventions when designing kernel modules? In other words, why are the =
> >drivers not modularized? Because my plan at least for the dectalk driver =
> >was to write the standard module code, and then dump the rest of the =
> >driver-specific code into the new re-written version. I am doing this =
> >for two reasons. 1. I want to keep the changes as error free as =
> >possible. 2. I don't want to have problems after writing new code. And I =
> >think most of the driver is fine the way it is. I have other reasons for =
> >modularizing the driver, including a project I am currently working on =
> >that requires this.=20
> >>  >=20
> >>  >=20
> >>  > _______________________________________________
> >>  > Speakup mailing list
> >>  > Speakup@braille.uwo.ca
> >>  > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>=20
> >> --=20
> >>          John Covici
> >>          covici@ccs.covici.com
> >>=20
> >> _______________________________________________
> >> Speakup mailing list
> >> Speakup@braille.uwo.ca
> >> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>=20
> >
> >
> >_______________________________________________
> >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

Re: speakup question

['Georgina']

Hi

As I asked.  Have you asked Kirk your question?  Maybe such a question
is a little advanced for the scope of a user list.  But you never know
there are some very tallented people on the list.

Gena



Blindness Advocacy and Self Help Online www.bashonline.org

>Hi. This is true. I just odn't have my box here right now so I can look =
>at the sourcecode. However, what I was looking for was exactly how =
>Speakup initializes itself during the boot process. For example, how is =
>Speakup able to start first in the boot sequence? Are the routines for =
>rs232 communication for external synths defined in speakup.h?=20
>----- Original Message -----=20
>From: 'Georgina' <gena@gena-j.net>
>To: <speakup@braille.uwo.ca>
>Sent: Monday, June 17, 2002 6:19 AM
>Subject: Re: speakup question=20
>
>
>> Hi
>>=20
>> I don't understand, you can view the source and for those synthesisers
>> that are not supported, perhaps you could get the specs and write
>> drivers yourself.
>>=20
>> Have you tried to ask Kirk specific questions?
>>=20
>> Gena
>>=20
>>=20
>>=20
>> Blindness Advocacy and Self Help Online www.bashonline.org
>>=20
>> >Hi John. This is all correct, however as far as I know the =
>synthesizer =3D
>> >driver is what's up before anything else. It would be nice to have =
>=3D
>> >documentation on exactly what Speakup does at boot time i.e., =3D
>> >synthesizer driver initialization, etc. This would help me a lot in =
>my =3D
>> >development, however such docs don't seem to be available. Looks like =
>=3D
>> >I'll have to dig up everything by hand.=3D20
>> >----- Original Message -----=3D20
>> >From: John covici <covici@ccs.covici.com>
>> >To: <speakup@braille.uwo.ca>
>> >Sent: Sunday, June 16, 2002 9:10 PM
>> >Subject: speakup question
>> >
>> >
>> >> The problem is that speakup needs to be alive before modules, =
>before
>> >> a file system and before much of anything except the console is
>> >> around.
>> >>=3D20
>> >> I understand Kirk is working on a scheme to allow modules, but if =
>its
>> >> a Dectalk pc, it won't talk at boot, but will have to wait till a
>> >> file is downloaded into it (at least that is my understanding, I
>> >> don't have one of those).
>> >>=3D20
>> >> on Sunday 06/16/2002 Igor Gueths(igueths@attbi.com) wrote
>> >>  > Hi all. Does anyone know why Speakup doesn't use the standard =
>=3D
>> >conventions when designing kernel modules? In other words, why are =
>the =3D
>> >drivers not modularized? Because my plan at least for the dectalk =
>driver =3D
>> >was to write the standard module code, and then dump the rest of the =
>=3D
>> >driver-specific code into the new re-written version. I am doing this =
>=3D
>> >for two reasons. 1. I want to keep the changes as error free as =3D
>> >possible. 2. I don't want to have problems after writing new code. =
>And I =3D
>> >think most of the driver is fine the way it is. I have other reasons =
>for =3D
>> >modularizing the driver, including a project I am currently working =
>on =3D
>> >that requires this.=3D20
>> >>  >=3D20
>> >>  >=3D20
>> >>  > _______________________________________________
>> >>  > Speakup mailing list
>> >>  > Speakup@braille.uwo.ca
>> >>  > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> >>=3D20
>> >> --=3D20
>> >>          John Covici
>> >>          covici@ccs.covici.com
>> >>=3D20
>> >> _______________________________________________
>> >> Speakup mailing list
>> >> Speakup@braille.uwo.ca
>> >> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> >>=3D20
>> >
>> >
>> >_______________________________________________
>> >Speakup mailing list
>> >Speakup@braille.uwo.ca
>> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>=20
>> _______________________________________________
>> 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 question

[Lui Greco]

[-- Attachment #1: Type: text/plain, Size: 262 bytes --]

if you toggle speech output off to avoid hearing the cursor position updates, then you won't be getting any feed back as to what your typing?  
That doesn't seem like such a good idea.

Lui Greco
Office: (506) 653-9725
Fax: (506) 657-5417 
www.fundycs.ca

[-- Attachment #2: Type: text/html, Size: 722 bytes --]

Speakup question

[Michela Botti]

Hi listers!
I have a newbie-question about speakup: is it possible to avoid that
speakup reads the line and column coordinates while moving the physical
cursor around the screen in a text editor, like, for instance, Joe, and
also while  typing the text?

Thanks in advance, Michela

P.s.: I started using Speakup only a few days ago with my Apollo 2 and I
want to thank Kirk and all his collaborators for the great work!
  

Re: Speakup question

[Kirk Reiser]

Hi Michela:  The best thing to do when cursoring around in an editor
if you don't want to hear the row and column changing is turn off
speech output with ins-kp_enter.  You can then turn it back on any
time you wish by doing the same thing.  It's a toggle.

I am glad to see the Apollo is working okay for you.  I still want to
get back to that driver at some point and try to make it even better.
That will have to wait for a while though.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Re: Speakup question

[Jim Wantz]

Hi Kirk and Michela,
Kirk, is this behavior limited to Jove, or perhaps some timing in the
Apollo driver?  I have not experienced this problem with the Transport,
Accent or Litetalk drivers.  It seems like I once had this problem with
some software in DOS with Business Vision, but I don't recall the
software.  Now, I'm going to have to get Jove to see if I have the same
problem.

     Jim Wantz


On 10 Jul 2000, Kirk Reiser wrote:

> Hi Michela:  The best thing to do when cursoring around in an editor
> if you don't want to hear the row and column changing is turn off
> speech output with ins-kp_enter.  You can then turn it back on any
> time you wish by doing the same thing.  It's a toggle.
> 
> I am glad to see the Apollo is working okay for you.  I still want to
> get back to that driver at some point and try to make it even better.
> That will have to wait for a while though.
> 
>   Kirk
> 
> -- 
> 
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: Speakup question

[Kirk Reiser]

Hi Jim:  It should happen in any editor which displays the row and
columns on the screen.  If you don't turn off speakup normal output
with the ins-kp_enter then those values get sent to the synth
everytime they get updated.

  Kirk

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061

Speakup question

[Dave Hunt <Dave Hunt]

You need to tell your editor, such as Joe, not to display a status
line.  There is, as yet, no way to silence a screen region like you
can in many DOS screen readers.  


--  Dave  --


Michela Botti writes:
 > Hi listers!
 > I have a newbie-question about speakup: is it possible to avoid that
 > speakup reads the line and column coordinates while moving the physical
 > cursor around the screen in a text editor, like, for instance, Joe, and
 > also while  typing the text?
 > 
 > Thanks in advance, Michela
 > 
 > P.s.: I started using Speakup only a few days ago with my Apollo 2 and I
 > want to thank Kirk and all his collaborators for the great work!
 >   
 > 
 > 
 > _______________________________________________
 > Speakup mailing list
 > Speakup@braille.uwo.ca
 > http://speech.braille.uwo.ca/mailman/listinfo/speakup