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.
As the OP of this topic you handled this discussion with admirable grace.
As I'm sure none of us has seen your company's application and the
project you inherited, we can only banter ideals and accepted best
practices with litle regard to their practical application.
I've found a lot of discrepancy between best practice and common use.
Most of these alternate practices derived from misinterpreted customer
feedback, lack of development time and money, and other factors.
Unless a product (documentation or other) is designed from the
beginning to be modular and object-oriented, there is a great chance
that additions will look more like a hobby construction project than a
I would consider the potential problems of multi level hierarchy, and
look for aternate ways to manage this. Maybe refer to each tab as a
specific function group, and avoid referring to the interface at all.
Maybe the model should becoming a living organism, where you are "in"
a (tab name) rather than accessing a function.
I keep imagining how the user manual must look for the computers used
in Minority Report or the flight controls in District 9 as examples of
the problems we're soon to encounter.
That said, you don't have to live your job. If you're stuck with tab
and subtab you could go with it, 35k hits or other.
Tony Chung: Creative Communications
Email: tonyc -at- tonychung -dot- ca * Web: http://tonychung.ca
Skype: tonychung.ca * GTalk/MSN: tonychung -dot- ca -at- gmail -dot- com
Twitter: @techcom * Facebook: http://www.facebook.com/tonychung.ca
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-