Keith Devens .com |
Friday, November 21, 2008 | ![]() |
| "Yes, it's terribly simple. The good guys are always stalwart and true, the bad guys are easily distinguished by... – Giles (BtVS: Lie to Me) | ||
|
| ← Some interesting news for today | YAML → |

pete (http://rasterweb.net/raster/) wrote:
August (http://dotmac.info) wrote:
As mentioned the Apple Human Interface Guidelines is a wonderful resource, but I think the best way to learn GUI design is to study interfaces that you like and don't like. Take the things you like an apply them, take the things you don't like and don't use them. Experience is the best teacher.
Keith (http://keithdevens.com/) wrote:
Thanks for the pointer to Apple's user interface guidelines, I'll check them out. However, that covers user interface design, not programming. I also wouldn't consider building web interfaces to be GUI programming. When building a web site one may have to make similar design decisions to those that one makes while designing a desktop application, but marking up a table in HTML is markedly (pun not intended) different than programming a Windows GUI in MFC or the Win32 API, or on OSX using Carbon, or in Java using Swing, etc. Those things take an entirely different skill set than being able to design a pretty interface or being able to mark up a web site in HTML.
Feel free to post a comment below. Please see my comment policy.
Formatting Rules (No HTML):
Generated in about 0.185s.
(Used 8 db queries)

Well, I consider building web interfaces GUI programming... But just in case you don't, and if you're looking for design and theory rather than code, look at Apple's Human Interface Guidelines.