Thanks. My boss thinks this guy is a wingnut. However, it is what it is. I've been invited to a meeting next Friday on the matter.
I think using tooltips for online help is 100% a bad idea; I cannot imagine what the 1% you mention could be. Accessibility is poor, as there is no TOC, IX, links between "topics," etc. There can be no graphics. Maintenance is a pain because you cannot globally format, spell check, etc. Usability stinks because the content disappears if you mouse off the control ... so for longer procedures, readers must make efforts to memorize the text, use SnagIt to grab the screen, etc. It is a business decision. Not sure what this guy wants. I bet, when the dust settles, nothing will change in the way we do online help currently -- which is uncompiled HTML with context senitivity provided by controlling filenames and using Aname bookmarks. Dunno. I'm amused by the whole thing. Thanks for the thoughts. Cheers, Sean -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Goldstein Sent: Friday, March 09, 2007 2:28 PM To: [email protected] Subject: Re: [TCP] samples of online help formats ... Hi Sean, The problem is, it isn't a bad idea in *every* case -- just in 99% of them. Your programmer is right *only* if nearly all of your users get help the same way. For most apps, users prefer a variety of methods: * Context-sensitive (popup, tooltip, right-click) * Full topic explanations for each important screen * A TOC based on app logic, structure, workflow, etc. * An index (tough to build but usually worth it) * Simple or Boolean searches It's a business decision based on company resources and user needs. I don't think there's a one-size-fits-all proof. Will your boss accept the argument above? Thanks, Dan > -----Original Message----- > From: Brierley, Sean > Sent: Friday, March 09, 2007 12:20 PM > To: TCP List > Subject: [TCP] samples of online help formats ... > > We have an omni-everything programmer who wants to document the > product using tooltips and only tooltips. Can anyone point me to > third-party document that explains why this is a bad idea?... > DISCLAIMER: Important Notice ************************************************* This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail.E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered with without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with IPC. IPC reserves the right, to the extent and under circumstances permitted by applicable law, to retain, monitor and intercept e-mail messages to and from its systems. ______________________________________________ Author Help files and create printed documentation with Doc-To-Help. New release adds Team Authoring Support, enhanced Web-based help technology and PDF output. Learn more at www.doctohelp.com/tcp. DOCUMENTATION & TRAINING WEST 07: THE USER EXPERIENCE April 18-21, 2007 ~ Vancouver BC ~ Marriott Pinnacle ~ free city tour 40+ sessions * free workshops * free iPod offer * www.doctrain.com _______________________________________________ Technical Communication Professionals Post a message to the list: email [EMAIL PROTECTED] Subscribe, unsubscribe, archives, account options, list info: http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com Subscribe (email): send a blank message to [EMAIL PROTECTED] Unsubscribe (email): send a blank message to [EMAIL PROTECTED] Need help? Contact [EMAIL PROTECTED] Get the TCP whole experience! http://www.techcommpros.com
