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.
Re: HTMLhelp vs. WinHelp (was Do users really like the format of HTML Help/Webhelp?)
Subject:Re: HTMLhelp vs. WinHelp (was Do users really like the format of HTML Help/Webhelp?) From:William Swallow <WSWALLOW -at- COMMSOFT -dot- NET> Date:Wed, 14 Jul 1999 11:44:56 -0400
I think you misunderstood my post. I am a strong advocate for HTML-based
documentation, whether it's Help, an online book or what have you.
I agree with you 100% concerning the benefits of HTML-based Help. I also
agree with your Web-application predictions. However, I don't agree that
HTML Help is the best solution for Web-based applications. A true
integration of Help in a Web application shouldn't call new windows or do
anything to take the user away from the application. I envision Web
applications eventually allowing space for text that dynamically changes
based on a user's actions, whether it be by pressing a Help button or merely
using the application - where you are in the application results in custom
links to info in the text area that are relevant to that point in the
application. Now THAT is user-oriented Help.
> -----Original Message-----
> Some bells and whistles are fluff. For example, an animated GIF with
> dancing dogs or a WAV file that plays everytime you enter a topic are
> obnoxious. However, there is so much more that HTML help opens the door
> to
> (as compared with WinHelp). For example:
>
