The Command Post
Global War on Terror
December 05, 2003
Bomb Aboard Russian Train Kills 36

From VOA:

Russia says it will find those responsible for a bomb attack on a commuter train near Chechnya that killed at least 36 people and wounded dozens of others ...

... The blast occurred in Russia's southern Stavropol region, aboard a train traveling to the town of Mineralnye Vody. The region borders the war-torn Chechen republic, where separatists have been engaged in guerrilla war with Russian forces for years.

Posted by Alan at December 5, 2003 07:05 AM | TrackBack
Comments

entirely off topic, but I see on foxnews there is talk of terrorists wrapping bombs in socks on their person, and thus not getting detected by security.
Maybe someone who knows can answer: if bombs can be in shoes, then why not just taped on the person? If that's true, then it seems like a big waste of time checking shoes at the airports.

Posted by: lucky at December 6, 2003 01:42 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: Didimus at January 24, 2004 12:19 AM

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: Wilfred at January 24, 2004 12:19 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: Archilai at January 24, 2004 12:19 AM

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: Simon at January 24, 2004 12:20 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: Annanias at January 24, 2004 12:20 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: Effemia at January 24, 2004 12:20 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: Jennette at January 24, 2004 12:20 AM

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: Roman at January 24, 2004 12:21 AM

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: Lancelot at January 24, 2004 12:21 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: Joshua at January 24, 2004 12:21 AM

Post a comment

Thanks for signing in, . Now you can comment. (Click here should you choose to sign out.)

As you post your comment, please mind our simple comment policy: we welcome all perspectives, but require that comments be both civil and respectful. We also ask that you avoid the extensive use of profanity, racist terms (neither of which we consider civil or respectful), and other boorish language.

We reserve the right to delete any comment, and to prohibit you from commenting on this site, if we feel you have broached this policy. As a courtesy, we will first send you an email noting a violation so you understand the boundaries. This will occur only once, however, and should we ban you from our comment forums we expect that ban to be permanent.

We also will frown upon those who suggest that we ban other individuals for voicing unpopular opinions, should those opinions be voiced in a civil and respectful manner. The point of our comment threads is to provide a forum for spirited though civil and respectful discourse … it is not to provide a forum in which everyone will agree with your point of view.

If you can live by these rules, welcome aboard. If not, then we’re sorry it didn’t work out, and thanks for visiting The Command Post.


Remember me?