« FireMonkeyyyyyyy | Main | Schedules »
June 19, 2003
QueryInTheFace?
Spent 2 hours figuring a issue, turns out it QueryInterface was misspelt as QueryInteface. Some other jolly misspellings:
QueryInTheFace
QueryInterfece
Need a xpcom spellchecker.
Posted by doron at June 19, 2003 10:48 AM
Comments
Personally I want a XUL/Javascript/XBL error checker. Loading Mozilla just to find that it doesn't work, with a non-descriptive error in the Javascript Console, is a pain.
Posted by: Ted Mielczarek at June 23, 2003 9:46 AM
User Assistance. This is helping the user with the proper "next step" when performing a task. Less guesswork for the user on what to do next makes for a better experience.
Posted by: Elias at January 25, 2004 10:18 PM
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: Blanche at January 25, 2004 10:19 PM
This topic is one we will tackle later in this article, but it refers to making sure that your application and the dock aren't fighting it out for supremacy of the screen.
Posted by: Meredith at January 25, 2004 10:20 PM
This topic is one we will tackle later in this article, but it refers to making sure that your application and the dock aren't fighting it out for supremacy of the screen.
Posted by: Holland at January 25, 2004 10:20 PM
To put my money where my mouth is, in each new article I'll build a hypothetical application that illustrates the guidelines I'm covering. Today's application is called "Paint" and will be based on the photo-illustrative icon I created in my last article. Together we will complete each step, and by the end of the project we should have a well-designed, 95%-100% Aqua-compliant application. I'll leave some room for personal preferences and the fact that Apple changes the OS every few months.
Posted by: Stephen at January 25, 2004 10:20 PM
Other examples of these animations might be to show the status of an FTP transfer, the progress of media being digitized, or an updated time signature. And don't forget that users may want to have some control over this, so give them plenty of options, including the ability to turn these functions off.
Posted by: Edmund at January 25, 2004 10:21 PM
Help! Did you include help tags in your applications? (I'd be lost without them.) Also, be sure to take extra time to develop your other help files. The Apple Help Viewer supports HTML, QuickTime, and also AppleScript. Take advantage of it! There isn't anything I hate more than going to the Help menu and finding there isn't any help.
Posted by: Cassandra at January 25, 2004 10:21 PM
Clicking 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: Eliza at January 25, 2004 10:22 PM
This is the first thing your users see, and probably the single most important visible part of your application. It is the first chance you have at making an impression and the best chance to help establish your brand.
Posted by: Harman at January 25, 2004 10:22 PM
This is the first thing your users see, and probably the single most important visible part of your application. It is the first chance you have at making an impression and the best chance to help establish your brand.
Posted by: Barnard at January 25, 2004 10:23 PM