home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!UB.com!pacbell.com!sgiblab!zaphod.mps.ohio-state.edu!uunet.ca!canrem!telly!robohack!becker!feline!king
- From: king@feline.uucp (KingLeon)
- Subject: Advice on Constructing Help Subsystem
- Message-ID: <1992Dec14.044553.26938@feline.uucp>
- Keywords: Help,Hypercard,Apple Events
- Organization: Humber College Technology Dept.
- Date: Mon, 14 Dec 1992 04:45:53 GMT
- Lines: 27
-
- I'm working on my lecture notes for a course on GUI programming. The
- course is a comparative study of the Mac and Windows. Currently I am
- working on a unit dealing with on-line help.
- Balloon help I find interesting, but very annoying - perhaps because
- it gets its message across too quickly and effectively, perhaps because
- all help is turned on when the user problably only wants to know about
- one item. Help is restricted to objects that are physically present.
- One can't ask about "how do I do this" kind of questions. Windows help
- launches another hypertext application (WinHelp) which has a terrible
- authoring environment and obscures the original application window.
-
- I recall that Apple at one time was pushing Hypercard as its help
- environment, but that didn't seem to take place.
-
- My question is as follows: What would a preferred method of adding
- Help to an application:
- 1. Launch Hypercard then send it a parameter or command either
- thru an Apple Event, global memory value or a keyword that
- is written to a a file?
- 2. Stick with Balloon Help?
- 3. There is some other technique that I've missed?
-
- Option 1 appeals to me because of the authoring environment of Hypercard,
- but some sample code would be helpfull.
-
- My students are 3rd year computer engineering. The course will be taught
- using standard (Think) C without the object extensions.
-