Re: XyWrite (Con't Cf. Msg# 10338

[Jim Jefferson]

Robert, well what can I say. The points you raise concerning the inherent
problems, which could be addressed and resolved if our developers had a break
in the schedule. I'm not going to offer *excuses* here, however I really do
not believe that it's a question of whether or not TTG wants to address certain
issues or change the way we handle certain features, it's a matter of
allocating our resources for the new products we are in development cycles
with, mainly General Councel. Now this certainly does not mean that XyWrite
will be discarded, just the opposite... XyWrite for DOS and XyWrite for Windows
are the base engines for our new generation products. We have been adding new
functionality to each, which will eventually flow into the mainstream XyWrite
word processors, primarily Windows. For problems inherent in the DOS version, I
try to push certain problems based on the severity, basically stating that
where DOS is concerned, proactive development is on hold (as you noted).
However, severe problems are looked at and addressed (we are now at revision
4.17e). I think I understand you position on these matters, but I can only
respond by saying that our survival in the software industry is directly linked
with our succes with our new generation products. My personal belief, and I've
been informed directly from the top, that XyWrite will continue. I also feel
that if we attain success with these products (which we are seeing right now)
we will be able to boost our Development staff and place further emphasis on
our mainstream word processing products as a result.

In the meantime, please forward problems such as the K,8,C - frame issues to
myself or Support, and we'll try to address them as best possible. If you find
issues such as noted above, which are important to the natural use of the user
(U#) files, I'll try to push such issues here in Development.

Regards, Jim J.