I am working in a reverse timeline here. That means, I am going to most
recently sent message backwards and responding as I go. Consequently, I
posted a rather nasty message about the docs for version 3.31 before reading
your acknowledgement of problems in that area; for that, I apologize. I
should have waited.
I have complained for years about the documentation not keeping up with the
programs at Henter-Joyce. I think my basic complaints are both relevant and
important. If we don't know that a feature exists, or what it is, or what
it does, then the feature might as well not be there.
This problem is most obvious in the script language documentation. Aside
from Ken Gould's excellent book "Everything you wanted to know about
scripts..." and Frank Depalermo's excellent "customizing jaws", there is
nothing to let us know about changes and enhancements to the scripting
language. Once again, if you aren't going to let us know what is available
in this area, then you shouldn't have released the script language for us to
use; and that would have been a real shame.
Thanks,
Bob
----- Original Message -----
From: Development Manager <[EMAIL PROTECTED]>
To: JFW Users List <[EMAIL PROTECTED]>
Sent: Friday, September 17, 1999 4:14 PM
Subject: Yes, We're Listening
> Hello JFW Users,
>
> Last night, after we put 3.31 up on our web site, I, along with a number
of
> other HJ employees, subscribed to this list and are reading the postings.
> We are trying to log as many of the bugs reported here as we can but, I
> must emphasize, that such reports should go to the address designated for
> the purpose of reporting your findings ([EMAIL PROTECTED]) as some of
the
> problems might otherwise fall through the cracks.
>
> I have enjoyed the general enthusiasm with which you folks have received
our
> new IE support. At HJ, we're all very proud of this version. I, for one,
> have noticed my internet habits change dramatically since I started
running
> the program about six weeks ago. The running joke around here is that
local
> cable companies should be giving us a kick-back for all of the new
> subscriptions to broad band services their getting from our employees.
>
> I have also noticed a number of problems with the documentation you
> received in build 22. I will take this opportunity to describe a few of
the
> omitted features (and give their associated keystrokes).
>
> A lot of you have mentioned that you would like to be able to jump passed
> the links at the top of a page. Our "Jump to Non-Link Text" feature is
> attached to INSERT+ENTER. This jumps to the next block of fifty or more
> characters which is uninterrupted by a link. We've done a lot of
> experiments to come up with this number but would certainly appreciate
your
> feedback about this threshold. If you are the sort who likes to manually
> edit configuration files, this value is called TextBlockLen and resides in
> default.jcf.
>
> A few people mentioned they would like to toggle between our new virtual
> mode and the way JFW did things in the past. This toggle is attached to
> INSERT+Z and seems to work pretty well. I have found this is most useful
in
> programs like FrontPage and other html editors. This also seems to work
> pretty well.
>
> You can route the JAWS cursor to the location of the virtual PC with the
> usual Route JAWS to PC keystroke. This will bring the approximate
location
> of the virtual cursor into view on the screen and turn on the JAWS cursor.
> Unfortunately, this is not working too well in build 22 and it will be
fixed
> before release.
>
> A couple of other documentation glitches that have been reported here are
> the result of our making changes to the program that did not get reflected
> in the documentation. The PC Cursor key, Numpad +, does not turn on forms
> mode, nor will it in the future. We did some experiments with this and it
> seemed altogether too confusing a keystroke. To turn on forms mode, you
can
> do a left mouse click (Numpad /) or hit ENTER on a forms field.
>
> The AutoCorrect feature of Microsoft Word did not make it into 3.31. We
> tried to get this working but we had far too many problems with it so we
> pulled it out of the product but it remains in the documentation. The
docs
> will have this removed in the next build and we will try to get the
feature
> into a future version of JFW.
>
> I also enjoy reading your suggestions. Formally, these should be sent to
> [EMAIL PROTECTED] to make sure none fall through the cracks. Our Product
> Manager reviews everything that comes to that address and these
suggestions
> become features in future versions of JFW. Sadly, we cannot get
everyone's
> favorite idea into the product but we do our best to get as much into
every
> release.
>
> Finally, I would like to take the time to thank all of you for downloading
> the software and reporting bugs and sending along suggestions. The input
we
> get from people like you is invaluable to helping us continue to make the
> world's most powerful screen reader even better.
>
> Thanks,
> Chris Hofstader
> Development Manager
> Henter-Joyce, Inc.
> [EMAIL PROTECTED]
> (727) 803-8000
>
> -
> Visit the jfw ml web page: http://jfw.cjb.net
>
-
Visit the jfw ml web page: http://jfw.cjb.net
