Stay current with the latest in tech comm
Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 5,000+ subscribers

Stitcher radio

Search results

Upcoming event:
I'm giving an API documentation workshop in San Francisco, California, on November 19, 2019. Check it out on EventBrite and register today to receive a $100 early bird discount.

Madcap Flare Spotlight -- "Six Persistent Flare Problems" Post by Paul Pehrson

by Tom Johnson on Jun 14, 2007 • 0 Comments
categories: technical-writing

Update Feb 2008: If you read Paul's post at the link below, almost everything is now crossed out, because Madcap has either fixed all the problems Paul raised or they explained workarounds. It's a really interesting read. Also, be sure to check out this podcast with Paul as well as my post on 45 Things I Love About Flare, 31 Things I Hate About It.

Paul Pehrson has an excellent post detailing six persistent problems he's encountered with Flare. Paul introduces his post saying,

I'm a Flare user, and I really, really, really like Flare as a help authoring tool (HAT). It's a solid program that does a lot of great things. On my recommendation, my company is going to renew our maintenance contract with Flare this fall, and I expect to be using Flare for a while to come.

That said, I think that there are a few persistent problems in Flare that new users should be aware of when they start using the product. None of these are deal-breakers for me, even in the aggregate. Still, I think that these are things that if I had known were problems, I wouldn't have spent hours banging my head against the wall trying to solve them.

Technically Speaking — Paul Pehrson's blog

I enjoyed Paul's post. Every tool has its shortcomings, quirks, and flaws that you don't experience until you start using the tool extensively. At least now if you go in the direction of Flare, you will be less likely to encounter surprises.

follow us in feedly