Internal Affairs: Highlight beeps

November 6, 2003

Highlight beeps

I just produced my first patch to X-Chat in order to fix a problem where actions containing my nick would highlight, but not beep if I have "beep on highlighted messages" enabled. This problem also exists for words contained in my "extra words to highlight" list which appear in action messages. I submitted it to zed, and hope to see it committed to the xchat2 tree.

Posted by caillon at November 6, 2003 7:57 PM

Comments

For example, if you see an AIM window peeking out from behind your browser and you click on it, that window will come to the front, but the main application window will not. The Mail.app/Activity Viewer is another example. The Aqua system of layers works well in many instances, but not in all. Thank goodness that the Dock is always there to come to the rescue. I know that clicking on an application icon in the Dock will always result in not only the application coming to the front, but also any non-minimized windows associated with it. And if the application is active but no windows are open, clicking on the Dock icon should create a new window in that application.

Posted by: Ralph at January 24, 2004 3:04 PM

Not quite as entertaining as Shrek, but Dock animation can be an important and useful function in your application. For example, Dock animation is a helpful way to indicate the status of your application.

Posted by: Isabella at January 24, 2004 3:04 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: Joos at January 24, 2004 3:05 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: Joshua at January 24, 2004 3:05 PM

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: Leonard at January 24, 2004 3:05 PM

Posted by: Tabitha at January 24, 2004 3:05 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: Isaac at January 24, 2004 3:05 PM

Whether native or not, this is obviously one of the first steps on your way to OS X. Keep in mind that often, the functionality of your code has a lot to do with how your interface is designed. How many developers have come up with great functional ideas from working with their interface or looking at their competitors'? Start working on your Aqua compliance from day one. Don't wait until the last minute.

Posted by: Hansse at January 24, 2004 3:05 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: Lionel at January 24, 2004 3:06 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: Holland at January 24, 2004 3:06 PM

great site, well done. very nice and informal comments. i enjoy being here.

Posted by: klaus at February 26, 2004 1:47 AM