TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
1. when opening the help file for WWP 6, it takes FOREVER to open (on a PIII
500, with 256 MB RAM, and a 32 MB display adapter, using Frame 5.5.6)
2. when attempting to generate a WebWorks Help file, it chokes and does not
produce a file, or produces an empty file, or produces a file with no images
(does it not support TIF conversion to GIF?)
3. in the one instance we were able to produce an apparently functional
Webworks Help file, it also took an inordinately long time to open. I can't
imagine our users waiting that long for a help file to open
4. We tried this on four different computers. Same result on each.
5. Quadralay's tech support response was to tell me that the new 2.0 version
of Webworks Help is Java, not Javascript, and that accounts for it taking
longer to open. But should it take THAT long? They also suggested I try
6.0.5, which I had already done, with no success. A final note on tech
support's response: they suggested that I could the Javascript-only
iteration (and gave me the modifier for the script), but said that the
Javascript version doesn't support "Favorites." Oddly, in 5.0.4, IIRC, that
was a Javascript version and it DID support "Favorites." Wazzup widdat?
Anyone else having these problems? Other problems? We're <this close to>
going back to 5.0.4 and demanding a refund on "Professional."
The real kick in the pants is how much Quadralay asked for the upgrade cost
when we'd just bought licenses for WWP 2000 three months ago. We thought: if
it gives us better cross-referencing and better support for inter-file
linking, it's worth it. Who knows if it does, but it adds new and WORSE
problems for us.
