Summary: WebWorks Help vs JavaHelp

[Steven Brooks <sbrooks -at- aw -dot- sgi -dot- com>]

Thanks to everyone who responded to my question. Because some replies
were offline, I
thought I'd summarize and also clear up some confusion.

* First, with all these funky HTML help names floating around, I should
clarify that "WebWorks Help" is a solution offered by
Quadralay for platform- and browser- independent HTML help. It's one of
the outputs supported by WebWorks publisher 2000,
which converts FrameMaker files to HTML.

* Although JavaHelp theoretically works with nonJava apps, most
responses confirmed that it's optimized for Java apps, because it
requires Java "stuff" that is more or less native to Java apps. (No, I'm
not a Java expert, but I think that's the gist.)

* Dependability does appear to be good for WebWorks Help. In response to
the question of what bugs I had found, I'll just bring up
the big one we encountered, which as of today still has Quadralay
stumped.
    - Open help in Netscape 4.x
    - Change to a subtopic.
    - Resize the browser.
    - The main frame jumps back to the opening image (top of the file).
    - (BTW: We're confident there's a workaround, but for now it's a bit
annoying.)

* My conclusion: if you're using Frame and looking for cross-platform,
browser-independent HTML help, WebWorks Help is a
fine solution.

-Steven Brooks
Alias|Wavefront
Documentation
sbrooks -at- aw -dot- sgi -dot- com