Eric.Bohlman@p1.f778.n115.z1.fidonet.org (Eric Bohlman) (01/08/91)
Index Number: 12663
[This is from the Blink Talk Conference]
If you run an at-home business doing Braille translation and production,
please send me your name, address and phone number (either here, in netmail to
115/778, or to the address below).
Toward the beginning of the new year I'll be releasing Tinytalk commercially,
and will need to make Braille manuals available. Hence I'm looking to find
out how much it will cost. I'd like to give my business to those who frequent
this echo.
The manual will also need a good bit of polishing from the present TTALK.DOC
that's being distributed; if you have good manual-writing skills, please
mention that in your message.
Eric Bohlman
OMS Development
1921 Highland Ave.
Wilmette, IL 60091
(708)251-5787 (voice; fax available on voice request)
--
Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!115!778.1!Eric.Bohlman
Internet: Eric.Bohlman@p1.f778.n115.z1.fidonet.orgEric.Bohlman@p1.f778.n115.z1.fidonet.org (Eric Bohlman) (01/11/91)
Index Number: 12865
[This is from the Blink Talk Conference]
Tinytalk has provisions to make it easy to set it up so that programs talk as
automatically as possible. For example, you can have it automatically detect
and read boxed windows that an application pops up. In addition to being able
to set up auto-monitor windows (watch windows in Tinytalk's terminology), you
can tell Tinytalk how the application uses those windows. For example, if an
application has a scrolling editor or file viewer in a window, you can specify
that that's the case, and Tinytalk will know that if text scrolls in the
window, it should read only the new lines that have scrolled in (we're talking
about windows that the application updates using direct screen writes).
There's also a mode for working with database forms that allows you to hear
the field prompt and value for the field that you're entering, and it works
even when there are multiple fields on a line (you hear only the one you're
currently working on).
Probably the most important feature, though, is minimal usage of RAM (16K).
The commercial version will include a set of add-in modules that you can load
along with Tinytalk to perform various functions. The purpose of making them
add-ins rather than building them into the program itself is that they perform
functions that some people really need but others don't want to bother with.
This way, you use only as much memory as you really need. One of the add-ins
will be a pronunciation exception dictionary; you don't need this if you're
using an external synthesizer that lets you store a dictionary in the
synthesizer's (rather than the computer's memory). Making it an add-in means
that you don't need to fill your memory up with it if you don't need it.
Another add-in will allow keyboard remapping and key labeling (possibly macros
as well). There will also be add-ins for advanced text reading (like forcing
a word processor to read continuously), number processing, scrollback
buffering and more. I'm hoping to include multitasker support in that version
as well. I also intend to supply pre-made configuration files for major
applications.
--
Uucp: ..!{decvax,oliveb}!bunker!hcap!hnews!115!778.1!Eric.Bohlman
Internet: Eric.Bohlman@p1.f778.n115.z1.fidonet.org