This link has been bookmarked by 34 people . It was first bookmarked on 24 Apr 2006, by Dan M.
-
Dave JefferyWYSIWYG Business card editor
-
Adrian BengtsonHur man jobbar med användarvänlighet (usability) för XMLHttpRequest i praktiken.
-
Two weeks ago I highlighted the most important usability issues with XMLHttpRequest. This week we are going a step closer to see how you can mix the two - including a practical example, just for the fun of it.
-
-
-
Two weeks ago I highlighted the most important usability issues with XMLHttpRequest. This week we are going a step closer to see how you can mix the two - including a practical example, just for the fun of it.
-
-
-
Two weeks ago I highlighted the most important usability issues with XMLHttpRequest. This week we are going a step closer to see how you can mix the two - including a practical example, just for the fun of it.
Normal forms are usable by default
1. You can clearly see where the input fields are, so you know what you can edit, and what you cannot.
2. It is forgiving. You can explore all you want because nothing is changed until you submit the data.
3. It lets you decide when to "save".
4. It confirms any action taken, since you are redirected to a different page upon completion. -
Two weeks ago I highlighted the most important usability issues with XMLHttpRequest. This week we are going a step closer to see how you can mix the two - including a practical example, just for the fun of it.
Normal forms are usable by default
1. You can clearly see where the input fields are, so you know what you can edit, and what you cannot.
2. It is forgiving. You can explore all you want because nothing is changed until you submit the data.
3. It lets you decide when to "save".
4. It confirms any action taken, since you are redirected to a different page upon completion. - 1 more annotations...
-
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.