RE: GoLive vs. Dreamweaver

[Mailing List <mlist -at- ca -dot- rainbow -dot- com>]

jsokohl -at- mac -dot- com [mailto:jsokohl -at- mac -dot- com] said:

> Funny, but I'd strongly recommend GoLive if you are worried more about
> designing pages, including interactivity. If you need
> compatability/integration with PhotoShop, Illustrator, and/or 
> InDesign,
> then GoLive's the way to go. Too, on the Macintosh OS, GoLive 
> is easier to
> use than Dreamweaver, IMO.

I assume that the discussion has been about web stuff, but 
what about authoring WebHelp?

I recently started using RoboHelp X4.1 to create WebHelp 
for our product that is used with multiple operating systems.
One of the first things that I heard on the HATT mailing 
list was:

"Of course, nobody uses the built-in WYSIWYG editor in 
 RoboHelp. Everybody uses DreamWeaver or some other 
 powerful HTML publishing tool instead."

But nobody has seen fit to lay out a point-by-point 
comparison of the advantages and disadvantages.

If/when our graphics/design guy leaves, I'll inherit his 
copy of DreamWeaver. Not sure how much use I'll have for 
it...

Is DreamWeaver or GoLive (or any of the others) capable 
of selectively creating/publishing output based on 
conditional settings? RH lets you mark content (or entire 
topic pages) with user-definable Condition Tags, which 
are then used to either include or exclude the marked 
material from output. I've already come to rely on that 
capability.

I know you can code all kinds of tests/conditions/selections 
in the page that an end-user sees, so that different things 
happen depending on what the user does, but the conditional 
settings that RH provides are more like what FrameMaker 
does -- they are compile-time choices that control the 
appearance of the published web pages.

I'd like to hear from somebody who's using DW or GoLive or 
other tool to create Help (specifically WebHelp).

/kevin