I am curious to know if EHelp collaborated with Adobe to produce this product, especially since Jorgen Lien, EHelp's Chairman and CEO, and Anthony Olivier, EHelp's CFO, just announced the Macromedia has purchased EHelp.
Hmmmmmm
2) Macromedia just announced they're buying eHelp, but the RHFM development began at least a year ago.
3) Don't know for sure, but I suspect not.
4) RHFM is a better approach than any other use of traditional RoboHelp plus FrameMaker.
Cheers,
Sean
The question I have is why Adobe, otherwise so obssessed with authoring tools for on-line content, hasn't developed or acquired equivalent tools of its own. Yes, Quadralay's WWP works well with FrameMaker, but it is a separate product, from a separate company, with a separate price, a separate user interface, and a separate support organization. The eHelp-for-FrameMaker product is no different in this regard.
Adobe's curse, I think, is its reliance on its Postscript fonts cash cow. It has made the company in many ways complacent and unresponsive to new business opportunities...
1. Others are doing it already, tying into FM, thus FM sales are supported with minimal extra dev allotted to another tool.
2. Adobe recognizes that a single-source authoring tool would probably benefit from much of the functionality in FM, but FM's code base is legacy and designed to really do one thing really well: print.
3. A plan for FM is probably if not already in the works, and without said plan, development of another tool is just wasted time for now. Adobe's doing funky things with FM down in India, so we'll have to wait and see what comes of that.
Not directly, but they are in my opinion related in the sense that Adobe's Postscript fonts cash cow enables the company's complacency. That complacency translates into the company's overly cautious approach to the authoring tools marketplace that so many of us find frustrating.
I can imagine the meeting of the Adobe strategists: "Look, my four-function calculator proves to me that it's too expensive to develop products. Besides, products have users and you know how annoying users can be. No, from where I sit developing, marketing, and supporting products, especially products that might have to compete, is just too risky. Let's just sit back and collect revenue on our fonts. We'll let other companies take the risk of developing the useful extensions our products need."
Yeah, I'm feeling a bit facetious this morning...