On the mountain bike ride the other day, Syd brought up a really good idea for keeping tests up to date that I should have remembered from my earlier corporate days: putting unit tests in the classes or files containing the code to be tested. The theory is sound: the same as API documentation, except it won't compile if you change the API. And it's a little easier to put the test there--a static method in the interface. Plus it encourages modularity--you have to think about your class a little more if the test has to be able to use it in isolation.
You could write a harness and have people just add their classnames and header files into it.
Posted by jkeiser at January 28, 2003 12:28 AMAdopt Sheets. I really like the use of Sheets in OS X. The use of Sheets lets me know which window my dialogue belongs to without hijacking my system.
Posted by: Laura at January 25, 2004 9:02 AMTo help you become a good Aqua citizen, Apple has created a few guidelines. I've put together a brief overview of them, and we'll be tackling many of them in the months to come.
Posted by: Annabella at January 25, 2004 9:02 AMAdopt Sheets. I really like the use of Sheets in OS X. The use of Sheets lets me know which window my dialogue belongs to without hijacking my system.
Posted by: Joos at January 25, 2004 9:03 AMClicking an application in the dock should always bring forward an active window. If the user clicks on an open app's icon in the Dock, the application is active and all unminimized windows come along with it. I have found a few problems with windows behaving independently of their application.
Posted by: Bartholomew at January 25, 2004 9:03 AMAdhere to File Locations. Make sure that when your users save documents, your application knows where to put them and also gives users flexibility.
Posted by: Jucentius at January 25, 2004 9:03 AMAt WWDC, I listened to Apple representatives make some excellent points about taking the time to build a 100%-compliant Aqua application, and I think all developers need to look beyond the code and listen to what the folks at Apple have to say
Posted by: Osmund at January 25, 2004 9:03 AMBy building an application that takes advantage of Aqua's many facets, you help ensure that your application will not only look good, but have a chance of becoming a raging success. After a new user clicks on the icon of your program, the first thing he or she sees is the application interface. I know that when I review a product, I am very critical of its visual design. I usually have a short time to learn the new software, so design and ease of use are very important. Aside from those who marvel at the beauty of the command line, most users tend to react the same way.
Posted by: Matthew at January 25, 2004 9:03 AMAdhere to Window Models. Document windows, Utility windows, Click-through, Layering, Drawers, Controls. How do users open windows, how do you properly title windows?
Posted by: Sampson at January 25, 2004 9:03 AMAdopt Sheets. I really like the use of Sheets in OS X. The use of Sheets lets me know which window my dialogue belongs to without hijacking my system.
Posted by: Lambert at January 25, 2004 9:03 AMDrawers. Similar to Sheets, this is a "child" window that gives users access to items that do not always need to be present. But when do you use a drawer and when do you use a palette?
Posted by: Christiana at January 25, 2004 9:04 AM