Just to throw some gasoline on the fire....
The title may be for s**t but there is a LOT of research into GUIs and how to present a screen so that it is easier
for ALL humans (read even the dumbest of us! ) to interact with a computer.
It does seem ludicrous (sp?) to write an entire article on the placement of Cancel or OK first, or whether the
Download button should be in the middle or on the right or left, but somebody has to decide
which side they go on, and if 1 program has the OK on the left, and then another has it on the right, and
yet another has the OK button in the middle, it may make for slower work for those who have a deep seated
fear of computers and all things IT.
Just to throw some gasoline on the fire....
The title may be for s**t but there is a LOT of research into GUIs and how to present a screen so that it is easier
for ALL humans (read even the dumbest of us! ) to interact with a computer.
It does seem ludicrous (sp?) to write an entire article on the placement of Cancel or OK first, or whether the
Download button should be in the middle or on the right or left, but somebody has to decide
which side they go on, and if 1 program has the OK on the left, and then another has it on the right, and
yet another has the OK button in the middle, it may make for slower work for those who have a deep seated
fear of computers and all things IT.
Just my 2 cents. It is a DUMB title though!
If you blindly click on the left hand button of every dialog you encounter then you deserve everything you get. Those who have deep seated fears of computers should get the hell away from them, for the sake of Pete.
Not necessarily true - I consider myself a fairly advanced PC user (network/system admin at work and programming in my spare time) but I was caught out recently when a dialog window had a button where you would normally place the Cancel button (I'm sure it was somewhere within VS) and I accidentally clicked it </NOOB>
If you blindly click on the left hand button of every dialog you encounter then you deserve everything you get.
Humans are good at spotting patterns and basing habits on them. I've been caught out many times by people putting Cancel and OK on different sides of each other.
So, silly as most VBWire articles are, this one is not so ridiculous.
(Some people don't understand the options "Save", "Don't Save", and "Cancel". Cancel what? Will my document be saved or not if I cancel? And on another note, what do the blue highlights in that OS X screenshot mean? Which button is the default option, and which is active? What will happen if I press Enter or Return or Space? It's complex to make simple interfaces.)
The thing is, if you screw up in Windows you usually have some kind of undo feature, because idiots (myself included) make mistakes.
However, on Ubuntu it assumes you know exactly what you are doing, which is a problem when you go to delete an couple of important database tables first thing on a Monday :/
However, on Ubuntu it assumes you know exactly what you are doing, which is a problem when you go to delete an couple of important database tables first thing on a Monday :/
The mere fact that people can blindly blow away a whole database is what keeps me employed. That is why I grant all of my users complete admin control to their own databases even though they barely know how to write simple queries!!! The stupidity of others keeps some of us employed.
the order is way less important than which button is marked as the default. I try to keep my hands on the keyboard at all times. The mouse is just for show
the order is way less important than which button is marked as the default. I try to keep my hands on the keyboard at all times. The mouse is just for show
true - I hate it when apps have a retarded tab order (ie, you are tabbing through the buttons and it jumps up to some button no where near the one you expected it to tab to next..)
It is best to just pop up two or three screens to prompt the user to verify that they really want to proceed - even then you will still have idiots who delete everything accidentally but you may cut down the number of times it happens by about 10%.
Does not explain (or even hint) that this class they are using is not actually part of the .NET framework and certainly doesnt mention that you have to pay for it!