Hi, I'd like your opinions on the following proposal from my product manager:
He'd like us to deliver all help screens as HTML pages installed on client machines or client app server, NOT as JavaHelp. Here are the pros, according to him: 1.. JavaHelp is difficult to produce (even with RoboHelp's assistance) 2.. JavaHelp is not actively supported by Sun. Its part of their 100% Java thing, but they have precious few resources devoted to making it better. 3.. We have to produce HTML before converting it to JavaHelp, so the JavaHelp step is an extra we may not need. 4.. I don't think our users will be confused by seeing HTML pages when they click help. 5.. Concentrating on making better HTML based help without the restrictions of porting it to JavaHelp will allow us to better leverage our Help/Doc/Spec efforts 6.. HTML-help will allow the transition to help for Web-clients easier. 7.. HTML-help will allow us to refer to further documentation maintained from the corporate website and provide a seamless transition to that content. And the cons: 1.. Would have to store the HTML help pages and images somewhere (either on client machine or on App server) 2.. User moving from client app to help and back means opening up their browsers 3.. JavaHelp is deliverable as a jar (or jars) installed along with everything else, HTML-based Help install would require something different. 4.. We'd would apparently lose the "100% Java" status I've not used JavaHelp for quite a while, so would appreciate some opinions from more recent JavaHelp users. Thanks in advance, -Paul _______________________________________________ Advanced-swing mailing list [EMAIL PROTECTED] http://eos.dk/mailman/listinfo/advanced-swing
