« Friday the 13th Part 1 | Main | je m'appelle (or is it je m'apple?) »
June 13, 2003
Mac IE is no longer.
And there was rejoice. yay.
Mac IE is being discontinued. Goodbye browser who lacked DOM support I always relied on.
Hopefully safari's DOM and JavaScript support will be better. However, this is really bad news for Gecko. Everyone on the Mac will move to embedding webcore and not embed the lizard.
Sad news for standards too, as Eric Meyer reminds me. The only part of Microsoft that cared about web standards is gone.
Posted by doron at June 13, 2003 2:04 PM
Comments
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: Edward at January 26, 2004 10:13 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: Jerome at January 26, 2004 10:13 AM
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: Ebulus at January 26, 2004 10:13 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: Cuthbert at January 26, 2004 10:14 AM
Adhere to Window Models. Document windows, Utility windows, Click-through, Layering, Drawers, Controls. How do users open windows, how do you properly title windows?
Posted by: Randolph at January 26, 2004 10:14 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: Gartheride at January 26, 2004 10:14 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: Randall at January 26, 2004 10:14 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: Salamon at January 26, 2004 10:14 AM
Adhere to Window Models. Document windows, Utility windows, Click-through, Layering, Drawers, Controls. How do users open windows, how do you properly title windows?
Posted by: Meredith at January 26, 2004 10:14 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: Thomasina at January 26, 2004 10:14 AM