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.
Subject:RE: Previous, Next and Print buttons in Help From:"McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com> To:Craig Haiss <craighaiss -at- yahoo -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 18 Jan 2010 13:47:32 -0500
About Browse Sequences, Craig Haiss said:
> Consider that the IE buttons behave differently than a browse
> sequence. IE's forward and back only move you through the
> history of the pages the viewer has visited. Previous and
> Next move you through a browse sequence determined by the
> help author (you), regardless of whether the visitor has
> viewed those pages already.
That's why I did my first WebHelp, years ago, with browse sequences.
But then we introduced variants on each product line that had
variant configuration steps and usage instructions, and I
sorta got out of the generated Browse Sequences in RH, and into
making my own with text links.
- If you have THIS version, go _here_ next.
- If you have THAT version, go _there_ next.
- If you have THIS OTHER version, stop now and upgrade... :-)
I never got back into the Browse Sequence habit when we
switched to Flare.
Should I?
Is it easy to have a long-ish sequence of instruction pages
that frequently splits into two or more paths that (sometimes)
later rejoin (or not), using Browse Sequences? Like, you'd start
with a single sequence, get to step/page 4 and there would be
three different page 4s, page 5s and page 6s, but then two of
those lines would rejoin at page 7, and the third would rejoin
at page 9... but then one would split off again.... another
would simply skip from 11 to 15... and like that.
Or does it become cumbersome to keep multiple intertwined BS
sorted and maintained?
- Kevin (who's not totally unfamiliar with BS...)
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-