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.
I don't think users know or care whether the three-pane UI is
generated by frames or something else. If you think your help looks
dated, you probably don't need to do anything other than revise the
CSS and maybe update some icons and other little UI graphics.
Adobe, MadCap, and other tools vendors have put a lot of effort into
new formats, "rich" media, and so on, but that doesn't mean those
features add value to every help system, or even most.
On Fri, Jul 22, 2011 at 1:33 AM, Tony Chung <tonyc -at- tonychung -dot- ca> wrote:
> Systems need to be more elegant to represent tri pane help in a single
> browser window. This system would need to be able to interpret a URL
> to show the correct subnavigation when users send URLs to individual
Huh? That's how it's always been. The "Webhelp" output formats
generated by WebWorks, RoboHelp, MIF2Go, and Flare have always used a
single browser window. They all support context-sensitive help via
URLs to specific topics.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-