Hi all
I would respectfully disagree to an extent with what GEWB
stated. While it's true that compiled HTML Help files use
components of Internet Explorer for the display mechanism, the
files being displayed are still HTML files nontheless. Aside from
folks perhaps coding them more loosely than your average HTML files
(because IE usually isn't all that persnickety with code) the files
inside are basic run of the mill HTML files.
I think to say that "Microsoft has created problems with HTML
Help files" is a fuzz misleading. This really typically applies to
files you place on a network server. Indeed, that functionality no
longer works. Files that are placed on your desktop or within your
Windows system (Vista or otherwise) should be fine.
Most browsers nowadays are already capable of playing Flash
(.SWF) content. And the same content may be used equally well from
inside a compiled .CHM file as with WebHelp. With WebHelp, if you
link to a Captivate .EXE, it won't simply play for you. Your end
user will typically see the standard "Whaddya wanna do with this
file? Run it from here or save it somewhere?" dialog each time they
click the link.
Essentially the driving factors are this:
Will your help file be shipped alongside an application that
is installed to the user's PC? If so, .CHM is likely your choice.
Will your help file be created to support an application your
user has to open off the web or a company intranet? If so,
WebHelp/FlashHelp is your choice. (Or maybe WebHelp Pro/FlashHelp
Pro)
Cheers all... Rick