[duxuser] Re: Duxbury and JAWS
- From: "George Bell" <info@xxxxxxxxxxxxxxxxxxx>
- To: <duxuser@xxxxxxxxxxxxx>
- Date: Sat, 4 Jan 2003 14:50:32 -0000
Hi all,
Before this topic gets a little out of hand, can I ask you all to please
try and provide specific instances where you believe problems exist,
rather than generalities. This is infinitely more helpful all round,
and allows the DBT development team to focus on what needs to be done to
fix the problem, and/or improve the product. I have already highlighted
the JAWS issues, and am confident that these will get serious attention
in the immediate future.
I'd like to explain the process in a little more detail if I may.
When a problem is reported, or a new feature suggested, it is entered
into a special development database held at Duxbury, where it is given a
category and rating based on content. Bugs usually do get the highest
priority rating.
And at this stage, let me assure you that the duxuser list is monitored
by Duxbury, and although I'm not directly employed by Duxbury, I do take
a very close personal interest in problems and new ideas, and try to
ensure that such things do get added. I know that other dealers do
likewise, albeit in a quieter fashion. (Smile)
The development database is continually examined, and tasks assigned to
individuals. When a particular item in the database is completed,
preliminary testing of that specific item can begin. Any further
problems found are reported back, and modifications made as required.
This is a virtual daily process.
However, it is seldom practical to provide an immediate release to
users. Many changes will have been made, and one change or fix, might
affect other areas further along the chain.
And so at some stage, determined by management, the project moves to an
Alpha testing cycle, where normal development stops, and the product is
tested, usually by internal staff. If no show stoppers are found, it
moves to the Beta cycle, where a wider group of carefully selected
people put it through it paces before final release.
In terms of the overall product, I would suggest that DBT faces quite a
challenge, especially in terms of accessibility. And I don't simply
mean "accessibility" in terms of visual impairment. I discovered this
only too well when authoring the Help files, which you all either love
or hate. DBT is used by as many fully sighted people as visually
impaired people, and short of producing two special products, (which
would doubtless raise more fury) development has to be done with both in
mind. However, at the end of the day, DBT is a Windows program, and so
follows Windows conventions as far as possible.
And DBT not only has to accommodate those who want quick and accurate
braille, but also those whose requirements call for special formatting,
languages, content, etc., etc..
However, DBT's most valuable asset is you, the user. If you tell
Duxbury what you specifically want, or have problems with, they can be
addressed. Don't expect things to happen overnight, or even in a few
weeks, but they will be done. Some things may be quick and simple to
do, others may mean far more investment in development time, and could
even reflect in the cost of the end product.
Before I close, I should refer to the topic a while ago about our own
"Wish Lists". Thank you all for your contributions. Without letting
too many secrets out of the bag, I know that quite a few things have
been done behind the scenes already for the next release. Editable
codes is just one.
So please keep the comments coming. Everyone is listening!
All the best,
George Bell
Techno-Vision Systems Ltd
* * *
* This message is via list duxuser at freelists.org.
* To unsubscribe, send a blank message with
* unsubscribe
* as the subject to <duxuser-request@xxxxxxxxxxxxx>. You may also
* subscribe, unsubscribe, and set vacation mode and other subscription
* options by visiting //www.freelists.org. The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *
Other related posts:
