« Real World Popups | Main | Introducing Spengler, a XUL based web service inspector »

August 19, 2003

What do you want?

Why do YOU read blogs? What do YOU want blogs to be about?

My guess is to feed your voyeuristic needs. Shame on you! Zip up and go help an old lady cross the street! And no peeking!

Posted by doron at August 19, 2003 4:04 PM

Comments

I read blogs because it's hard to keep track of mozilla developement

Posted by: alanjstr at August 19, 2003 6:27 PM

Yeah, me too. And also because sometimes bloggers post interesting links.

Posted by: Ariel at August 20, 2003 6:51 AM

I'm in it for the goat pr0n links.

Posted by: Ted Mielczarek at August 22, 2003 5:10 AM

i imagine most people make their way here b/c you're a mozilla developer, so commentary and updates about mozilla things are always fun.

Posted by: louis bennett at August 25, 2003 6: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: Rees at January 25, 2004 10:43 PM

Adopt 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: Rose at January 25, 2004 10:43 PM

At 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: Abacuck at January 25, 2004 10:43 PM

You Must Promise. To call your mother, to help old ladies cross the road, and to turn your cell phone off at the movies.

Posted by: Aveline at January 25, 2004 10:43 PM

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: Miles at January 25, 2004 10:44 PM

For my Paint application, I created a series of icons to simulate a rendering algorithm. While the application is performing this CPU-intensive task, you can always see the status of the document by the icon changing in the Dock.

Posted by: Guy at January 25, 2004 10:44 PM

Dock Animation. Sometimes animating icons in the dock can be useful in communicating the status of the system or application.

Posted by: Ambrose at January 25, 2004 10:44 PM

For my Paint application, I created a series of icons to simulate a rendering algorithm. While the application is performing this CPU-intensive task, you can always see the status of the document by the icon changing in the Dock.

Posted by: Ellis at January 25, 2004 10:44 PM

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: Cornelius at January 25, 2004 10:44 PM

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: Lettice at January 25, 2004 10:44 PM