This content has been marked as final. Show 6 replies
Welcome to the forum
Those are your options. You pays your money and you takes your choice.
The CHM restrictions can be overcome as described on my site but it is not really the route to go. You might upset some customers!
Yes webhelp has lots of files but they are all off one folder and its subfolders so it is reasonably contained. Because you can use skins, it looks much more professional.
There are lots of people using it and it is the correct format for your scenario.
Thank you for the comments.
One thing I forgot to mention: our application is built on Sybase PowerBuilder 10.5 and uses the built in function to call our help system. According to the Sybase documentation, the built in function (ShowHelp()) ONLY knows about WinHelp and HTML Help...so I'm not sure we can even launch WebHelp from our application. If anyone knows of a resource for PowerBuilder / WinHelp integration, I'd appreciate the mention.
BTW, I am aware that WinHelp is usable in Vista (I've set up my own machine for it), but I think we're hoping not to force our customers through that installation hoop...
Hi chitwngman. First of all let me qualify my comments by saying I am not familiar with Powerbuilder. If that is what the documentation says then I'm not going to argue. Would an upgrade to a newer version of PowerBuilder solve the problem? If not, you seem to be stuck with the CHM or Winhelp scenarios.
There's always the fall-back with WebHelp - calling topics by URL, rather than through an API. It makes the programmers complain about the extra work, but it's relatively straightforward.
There's a good explanation of this on Peter Grainge's site www.grainge.org. Hope it helps.
Elisa's right: calling the URL works for PowerBuilder, or even a combination of PB and C#.
For context-sensitive calls, they must go through your start page to get the navigation frameset ( ex: MyStartPage.htm#MyTargetTopic.htm).