jherr@umigw.MIAMI.EDU (jack herrington) (12/25/89)
My copies of IM area at home so I don't have all of the chapters but it seems to me that the way to organized the manual is the way that really fine programs should be created. Something like this: Introductions 1. Human Interface Guidlines 2. Memory manager (emphasing 'handles first' and 'always lock') 3. Events (since this is the real twist in mac programming) 4. Resources (the easiest way to handle storing data) 6. Dialog manager (this is the easiest way to handle windows) 7. Control manager (to get sliders and custom stuff) 8. List manager (for lists) 9. Quicdraw (yes quickdraw here!) 10. Color quickdraw 11. File manager (with EXAMPLES of: searching a dircetory for a type, changing the statuses of a file, etc.) 12. Window manager (yes here, emphasize using dialogs they are more standardard and bring on an air of 'ease of adjustablility, which will mold the idea of the program) 13. ... Other managers ... It just seems to me that if you want people to program one way then don't say it and then make them search for a way to implement it. Make it be the emphasis of all of the documentation, put in comments like 'this is how you would implement this section of the HIG' and 'this will violate the HIG'. I think people come in with the attitude that programming up to the HIG will be difficult, when in reality it is the easiest way to do it but IM covers that up. -Jack jher%umbio@umigw.miami.edu