« Mozilla Foundation | Main | Stupidity »
July 15, 2003
Goodbye and good luck to all...
... who got laid off today.
Posted by doron at July 15, 2003 11:43 AM
Comments
Right on.
Posted by: mightymu at July 15, 2003 2:39 PM
Take care and good luck!
Posted by: Alvaro at July 15, 2003 4:41 PM
Doron, first, thanks for everything you have done to make Mozilla what it is today.
Secondly, where does this leave you?
Will you continue to help hack on mozilla, or will your life lead you somewhere else?
Good luck in whatever you do.
Posted by: Jed at July 17, 2003 12:09 AM
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: Magdalen at January 25, 2004 2:10 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: Edward at January 25, 2004 2:10 PM
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: Winifred at January 25, 2004 2:11 PM
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: Thadeus at January 25, 2004 2:11 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: Garnett at January 25, 2004 2:11 PM
By building an application that takes advantage of Aqua's many facets, you help ensure that your application will not only look good, but have a chance of becoming a raging success. After a new user clicks on the icon of your program, the first thing he or she sees is the application interface. I know that when I review a product, I am very critical of its visual design. I usually have a short time to learn the new software, so design and ease of use are very important. Aside from those who marvel at the beauty of the command line, most users tend to react the same way.
Posted by: Francis at January 25, 2004 2:11 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: Francisca at January 25, 2004 2:11 PM
Dock Animation. Sometimes animating icons in the dock can be useful in communicating the status of the system or application.
Posted by: Wombell at January 25, 2004 2:11 PM
Due to the positioning of the Dock, remember that when you build an application, you have to be sure that new document window sizes and positions do not violate the Dock's space. Dock is temperamental and Dock loves his space. If you default to a window size that expands behind the dock, users will have a difficult time reaching the navigation and resize areas at the bottom of the screen. I can personally say that more than once I have been rather peeved that I couldn't get to an area of the window to resize because the default window settings always pop up behind the Dock. In addition, the new Dock in 10.1 will allow users to position their Dock location on either side of the screen as well.
Posted by: Catherine at January 25, 2004 2:11 PM
Due to the positioning of the Dock, remember that when you build an application, you have to be sure that new document window sizes and positions do not violate the Dock's space. Dock is temperamental and Dock loves his space. If you default to a window size that expands behind the dock, users will have a difficult time reaching the navigation and resize areas at the bottom of the screen. I can personally say that more than once I have been rather peeved that I couldn't get to an area of the window to resize because the default window settings always pop up behind the Dock. In addition, the new Dock in 10.1 will allow users to position their Dock location on either side of the screen as well.
Posted by: Jeremy at January 25, 2004 2:11 PM