August 24, 2003
Thinking about a new vehicle
I'm starting to question my need to get an STi. It really doesn't have the capacity and the utility that I need. My new desire is a bit older, more broken in vehicle. That vehicle, is a 4x4 toyota van. Now, you may question my sanity, but until you see one of these smoke a G35 at a light, you don't know what you're missing!
Posted by kerz at August 24, 2003 6:42 PM
Comments
i owned a toyota van. only got rid of it because i dont have much use for a car at the moment, and needed some extra cash. i'd definitely get another though... so go for it, woop :]
Posted by: andrew saturn at August 25, 2003 4:13 AM
I just bought an older STi (I'm sure Ben's looking forward to a joy ride when he gets back to NZ). I'm pretty sure that your 2003 STi will have more trunk space than my 1998 STi coupe, and I can cram a bicycle into mine. And you can never have enough overtaking power and grip, period. Smoking a G35? Who knows! Go the STi.
Posted by: Simon Chong at August 26, 2003 3:46 AM
Drawers. 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: Rose at January 24, 2004 7:43 AM
The simple fact is that, when all other factors are equal, where will consumers spend their money? I believe that in the long run, the best looking, easiest-to-use applications will also be the most successful. I think that's why Apple encourages developers to write programs that are 100 percent Aqua-compliant.
Posted by: Griffin at January 24, 2004 7:43 AM
If an application is designed well, the reward for users is that they will learn it faster, accomplish their daily tasks more easily, and have fewer questions for the help desk. As a developer of a well-designed application, your returns on that investment are more upgrade revenue, reduced tech support, better reviews, less documentation, and higher customer satisfaction. The rewards of building a good-looking Aqua application are worth taking the extra time.
Posted by: Bertram at January 24, 2004 7:44 AM
So far in these articles, I have only dipped a toe or two into Aqua's pool. I have covered basic aspects of building an Aqua-compliant application, including the building of photo-illustrative/3D application icons. Now it's time to address other components of our Mac OS X application.
Posted by: Gabriel at January 24, 2004 7:44 AM
The simple fact is that, when all other factors are equal, where will consumers spend their money? I believe that in the long run, the best looking, easiest-to-use applications will also be the most successful. I think that's why Apple encourages developers to write programs that are 100 percent Aqua-compliant.
Posted by: Gerrard at January 24, 2004 7:44 AM
In building your amazing Aqua application, one of the most important things to consider is the Dock. There are three things your app needs to be "Dock Compliant." Now, I write this knowing that the Dock will be going through some major changes soon, but for the most part, these should still hold true.
Posted by: Cassandra at January 24, 2004 7:45 AM
But limit your animations to whatever is required to communicate the necessary information. Avoid annoying animations that discourage ease of use. Ask yourself, "What do I need to show the user, and what is the cleanest way possible to achieve that?" A good example is the Mail application for Mac OS X. Whenever a new message arrives, the Dock icon changes appearance to indicate a changed state.
Posted by: Lancelot at January 24, 2004 7:45 AM
Okay, I just told you what Apple wants you to look out for with window positions, but in the real world, not everyone uses the hiding feature of the Dock, and it is unrealistic to be able to predict where each user will place their Dock at any given day or how large they will have it. However, you can build a feature into your application that allows spacing for the Finder. You can give users the option of where to position their windows and what area of the screen not to cross. I know that BBEdit provides me with this feature, and I wish more developers gave me more control over my windows.
Posted by: Aaron at January 24, 2004 7:45 AM
Okay, I just told you what Apple wants you to look out for with window positions, but in the real world, not everyone uses the hiding feature of the Dock, and it is unrealistic to be able to predict where each user will place their Dock at any given day or how large they will have it. However, you can build a feature into your application that allows spacing for the Finder. You can give users the option of where to position their windows and what area of the screen not to cross. I know that BBEdit provides me with this feature, and I wish more developers gave me more control over my windows.
Posted by: Cadwallader at January 24, 2004 7:46 AM
Adhere to Layout Guidelines. Did you leave 12 pixels between your push buttons? Does the positioning of your pop-up menus make sense, and when do you use a pop-up versus a scrolling list? Are you using the right types of buttons for the proper functions?
Posted by: Hieronimus at January 24, 2004 7:46 AM
Truth is a kind and gentle lie.
Posted by: credit report at February 1, 2004 6:33 AM