It's best to use Apple's help. However, you may want to consider the case where your app supports a localization that Apple's Help app doesn't and give the user the option of opening your help pages in the user's web browser. In one app some time back, the help would show English while the user was running Turkish. That particular case may be workable now, but a similar one may occur. See how Apple does this in Xcode for their documentation viewer. -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/
> On Apr 29, 2014, at 10:52 AM, Gordon Apple <g...@ed4u.com> wrote: > > We would like to get a recommendation on the best way to generate a help > system for a fairly complex application. We started by using a simple web > view and created about 120 screens in BBEdit, mostly drill-down outlines. > Unfortunately, this has been proven to be difficult to maintain. We¹ve > looked into web generators like RapidWeaver, Freeway, and even Dreamweaver, > but all of these have been described as ³roach motels² where you enter but > can never leave. > > We would like to have both local and web-based or web-updated content and > have contextual help. This all brings us to Apple¹s ³Help Book², which seems > to have been around forever and presents its own learning curve. So the > question is: Is this the way to go? It it still current? What are the > experiences in using it? _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
