Bugs in Gurgel Doll 1.0
HAHAHAHAHAHA!!!!!!!!!!!! This is TOO funny.
When you open the 'View Gurgel Doll' window, it says "Your Gugel Doll" on top of the window! Look! It really does!
And when you put the cursor on top of your doll's HAND, it says "Your Gurgel Doll's chest."
<img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <img src="graemlins/lol.gif" border="0" alt="[Laughing]" />
(Go on, look!)
[ 10-17-2002: Message edited by: Hassan i Sabbah ]</p>
When you open the 'View Gurgel Doll' window, it says "Your Gugel Doll" on top of the window! Look! It really does!
And when you put the cursor on top of your doll's HAND, it says "Your Gurgel Doll's chest."
<img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <img src="graemlins/lol.gif" border="0" alt="[Laughing]" /> <img src="graemlins/lol.gif" border="0" alt="[Laughing]" />
(Go on, look!)
[ 10-17-2002: Message edited by: Hassan i Sabbah ]</p>
Comments
<strong>HAHAHAHAHAHA!!!!!!!!!!!! This is TOO funny.
When you open the 'View Gurgel Doll' window, it says "Your Gugel Doll" on top of the window! Look! It really does!
And when you put the cursor on top of your doll's HAND, it says "Your Gurgel Doll's chest."
</strong><hr></blockquote>
1st: I never proof-read my work before I turn it in
2nd: The actual image region is for the Gurgel Doll's chest, so the middle part of the gurgel doll is comprised of 1 image, the head is another, and the legs are another...
<img src="graemlins/smokin.gif" border="0" alt="[Chilling]" />
Early adopter.
Sorry.
<strong>My bad.
Early adopter.
Sorry.</strong><hr></blockquote>
no, i do not believe it is that. It is my bad for not checking the spelling. But the "gurgel doll's chest" is just how the program is... maybe I should replace that word, eh? <img src="graemlins/smokin.gif" border="0" alt="[Chilling]" />
Linkage? <img src="confused.gif" border="0">
<img src="graemlins/smokin.gif" border="0" alt="[Chilling]" /> <img src="graemlins/smokin.gif" border="0" alt="[Chilling]" /> <img src="graemlins/smokin.gif" border="0" alt="[Chilling]" />
Well, if that's true, then I have a single suggestion for your future apps.
Please read and try to follow Apple's HI guidelines.
The non-adherence to interface norms makes your app look like a very alien and weird amalgamation that was spawned as a port of an even weirder Windows app. It's just confusing.
<img src="confused.gif" border="0">
<strong>Okay, I downloaded it and tried it out. I will certainly agree with the readme that this app serves no real purpose. I can only guess the you built it as a tutorial to learn to write an app. Is this right?</strong><hr></blockquote>
nope
<strong> [quote]
The non-adherence to interface norms makes your app look like a very alien and weird amalgamation that was spawned as a port of an even weirder Windows app. It's just confusing.
ok
<strong>ok
* First, when making buttons, always choose "size to fit" in Interface Builder after enter text into them. This will resize them to properly fit Apple's guideline.
* Don't use a lot of separate layers of boxes or rectangles with hard borders and opaque (or even partially opaque) backgrounds to separate the elements on the screen. A simple gap of "white space" can be just as effective and will look far more elegant.
* Don't use an NSTabView unless you're actually using tabs! Again, it's not meant to be used as a box just to emphasize something.
* Use standard Aqua push buttons whenever possible. Only use the beveled button when you have an icon you also want displayed on it or it has a radically different function than a regular button. Take a note from Apple's own apps for this one -- just how often to you see the bevel button in them?
* Always use black text in the UI unless you *really* want to emphasize something. The light blue text in the FAQ drawer is nearing on unreadable.
* Don't repeat main labels as you do on the first screen of your app. Only an inch apart, it displace the same Welcome message *twice*.
* To follow up on the last point, a welcome message should probably only be presented on the initial screen, not throughout the entire app.
* Use the "Bold System Font" for major headings like the Welcome text. Be careful not to overuse bold, though.
* You should probably use Apple's own forward and back buttons from the Finder. Don't be afraid to steal some of their images! Heck, even the Omni Group steals and uses Apple's UI images in its apps. Remember the old motto "good artists copy, but great artists steal."
* Only use drawers for supplemental information. A FAQ can be considered supplemental, but putting it in a drawer is bad design because it means the drawer has to be kept open to a long time. A FAQ would be much better suited in the help file. Also, if you find you are making drawers that are as big or bigger than your main window, that should be a clue that there's something wrong with the design.
* Redundancy is okay in moderation, but don't go overboard. Adding buttons for functions like "close window" or "quit" are simply unnecessary because anyone who has used a Mac for 10 minutes will know the proper way to close a window or quit an app.
* Find a shorter string to use as the Application Menu's title. Another cue you should note that there's something wrong with a UI design is when a menu title is a third longer than any of its menu items.
* Always proofread your app before stamping the "ok" on a final version! Spelling errors and inconsistent naming just SCREAM "bad UI!"
* Also, always check to be sure all your buttons and menu items work at least most of the time. There is an item "FAQ" in the help menu that never does anything.
* Remember that you can also use tooltips to provide supplementary information. A simple tooltip would probably fit better than the big "Help" button next to the age. Also, how many people do you really think will need help entering their age?
* Whenever possible, provide feedback about bad data in entry fields *before* moving to the next screen. I was able to choke the app very easily by entering single characters into the various fields. It didn't notify me that something was wrong until the very end and even then it didn't properly tell me what to correct or how to correct it.
* Keep buttons that are "global" in the same location. The back button jumps around on each section of the app.
And remember the most important UI rule on the Mac:
KISS (keep it simple, stupid
The Mac OS is all about simplicity. Don't arbitrarily add a bunch of UI elements and clutter without heavily weighing the consequences. They will quickly add up to become confusing and irritating to the user. Take the time to carefully think about and consider the consequences of EVERY user interface element in your app. Look at something before adding something or changing the standard look or behavior and ask yourself, "is this really necessary?"
I hope you don't take this is "ragging" on your app.
[ 10-18-2002: Message edited by: Brad ]</p>
'kid, I love the Gurgel Doll Production Factory.
I was only joking when I kicked the thread off. (I was going to start a "Gurgel Doll Production Factory 1.1 Wishlist" thread next, but I fell asleep.)
Having said that, erm, Brad: you know you shit, innit? Crikey.