Hi,
A friend of mine mentioned this thread and suggested that I
reply.
The seminar covers the state of the HAT market, and is as
factual as any such discussion can be these days. I've been giving
this seminar for nine months, starting before Adobe came on the
scene and when it looked like Macromedia was killing it. So the
point of the seminar was to explain what happened to RoboHelp,
discuss examples of new tools, and offer tool selection criteria
for new tools.
Because of the recent upheavals - the big one being Adobe's
announcement of support for RoboHelp - the seminar has to be very
flexible. Wednesday's discussion will cover the same points that I
listed in the previous paragraph but more broadly. The point,
again, is that the HAT world is changing, with the biggest change
being the uncertainty around RoboHelp - will Adobe release X6, with
what features, when, and whether it will be competitive with the
newer XML-oriented tools.
I'll note that I've been in tech comm for 27 years, hypertext
for 21, Windows-based help for 17, HATs for 15, and RoboHelp for
15. I've been training and consulting on RoboHelp specifically
since 1995 and was one of the first eHelp certified instructors.
I've also been ForeHelp certified and was one of the first Flare
certified. With that background, several points re some of the
responses you've gotten:
- By 2003, RoboHelp had beaten all of its former competitors,
had about 80% of the HAT market, and played a major role in setting
the market's direction. The vast majority of my clients, and fellow
consultants' clients, used RoboHelp and had barely heard of any
other tools. That's stability.
- I'm not surprised that I missed Help & Manual and I've
probably missed some others. No presentation will ever be 100%
comprehensive.
- My experience is that demand for RoboHelp training has
dropped like a rock. I base this on feedback from two MATPs and my
own consulting/training practice. People are holding off to see
what's going to happen.
- Re the disagreement with my point about how a move to an
XML tool will let us clean up bad projects and workflows. No, the
move to an XML tool offers us *the opportunity* to clean up bad
projects and workflows. However, I will note that the move from RTF
to HTML eliminated some major problems in the old WinHelp simply
because of the difference in technologies.
- Finally, RoboHelp *has* been surprisingly stable and robust
given the fact that the code has barely been touched in over two
years. This is a testament to the quality of the work that went
into X5. However, it is starting to break, sometimes in odd ways.
Hope this helps.
Regards,
Neil Perlin