Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!ncar!asuvax!stjhmc!p88.f15.n300.z1.fidonet.org!Lawson.English From: Lawson.English@p88.f15.n300.z1.fidonet.org (Lawson English) Newsgroups: comp.sys.mac.programmer Subject: Mac Programming Book Wanted. Message-ID: <5918.27EB6EA5@stjhmc.fidonet.org> Date: 22 Mar 91 15:43:21 GMT Sender: ufgate@stjhmc.fidonet.org (newsout1.26) Organization: FidoNet node 1:300/15.88 - Tucson Apple Core, Tucson AZ Lines: 26 mguyott@eriador.prime.com writes in a message to All M> We are getting ready to port our product to the Mac and I am M> looking for a book that will give me a good starting point When porting your prog to the Mac, pay very close attention to the Mac User-Interface Guidelines. Reviewers of Mac software love to rip applications to shreds when they don't follow the guidelines. For instance: the Windows habit of creating "hot-keys" in a dialog by using the first letter of the title of a button doesn't work well on the Mac as certain cmd-key combinations are already taken, such as cmd-c for Copy or cmd-o for Open. If you used "o" for "OK" or "c" for "Cancel", you might confuse lots of folks. Use for the (hilited) default button, and cmd- for Cancel (assuming that it's not the default...) and you will find that users will accept your application more readily... (Almost) every volume of "Inside Macintosh" has a chapter on the Mac Human-Interface Guidelines and there is a seperate book from Addison-Wesely that addresses this issue. Lawson -- Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!300!15.88!Lawson.English Internet: Lawson.English@p88.f15.n300.z1.fidonet.org