(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 
View Attach Info

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-20) was last changed on 04-Mar-2008 04:37 by 129.78.64.101  

This page was created on 01-Feb-2007 13:02 by ChristophSauer

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 changed 4 lines
zelracdelal
In these days when processor power is cheap and programmers are serving the whole world, it's all too common to see systems requiring input based on how the system works, instead of how people work. This user-unfriendly approach exposes these systems to competition fr
2000
om products that are nicer to their users, though we might view them as technically inferior.
In these days when processor power is cheap and programmers are serving the whole world, it's all too common to see systems requiring input based on how the system works, instead of how people work. This user-unfriendly approach exposes these systems to competition from products that are nicer to their users, though we might view them as technically inferior.
At line 11 changed one line
* Collaborate on user interface design. (Hey! - we're back where we started.)
* Collaborate on user interface design.
At line 14 changed one line
This doesn't mean that you should never require specific format or duplicated data -- they can have their own uses.  For example, when changing your password, you're prompted to enter it twice.  This serves to verify a concealed entry and avoid losing system access. This is close to [[http://en.wikipedia.org/wiki/Poka-yoke|poka-yoke]], so it's OK. Similarly, if the input files are to be heavily edited by various people, then it's good to keep them readable by restricting markup syntax, stripping formatting markup added by word processing bloatware, etc. Of course, such a strict syntax should be paired with validation, and a good, non-destructive way of indicating errors.
This doesn't mean that you should never require specific format or duplicated data -- they can have their own uses.  For example, when changing your password, you're prompted to enter it twice. This serves to verify a concealed entry and avoid losing system access. This is close to [[http://en.wikipedia.org/wiki/Poka-yoke|poka-yoke]], so it's OK. Similarly, if the input files are to be heavily edited by various people, then it's good to keep them readable by restricting markup syntax, stripping formatting markup added by word processing bloatware, etc. Of course, such a strict syntax should be paired with validation, and a good, non-destructive way of indicating errors.
At line 20 changed one line
There are also some advices useful for web browser and wiki engine developers:
There are also some pieces of advice useful for web browser and wiki engine developers:
At line 26 changed one line
** Allow users making incomplete entries to save them and finish them later.  Do this automatically for users that time-out.
** Allow users making incomplete entries to save them and finish them later. Do this automatically for users that time-out.
At line 40 changed one line
However, Creole is a markup standard, and as a standard it should never change dramatically and become incompatible with itself in the feature. The things we specify must be final, so that Creole is not a moving target for the developers and constant confusion for the users.
However, Creole is a markup standard, and as a standard it should never change dramatically and become incompatible with itself in the future. The things we specify must be final, so that Creole is not a moving target for the developers and a cause of constant confusion for the users.
Version Date Modified Size Author Changes ... Change note
20 04-Mar-2008 04:37 4.54 kB 129.78.64.101 to previous speling missteak
19 21-Oct-2007 12:13 4.571 kB RadomirDopieralski to previous | to last restore
18 21-Oct-2007 05:15 4.58 kB 210.17.247.39 to previous | to last
17 26-Sep-2007 09:33 4.571 kB ChuckSmith to previous | to last restore
16 26-Sep-2007 01:10 4.61 kB 203.69.39.251 to previous | to last
15 26-Sep-2007 01:09 4.592 kB 203.69.39.251 to previous | to last
14 22-Feb-2007 02:46 4.571 kB JimGettman to previous | to last
13 08-Feb-2007 10:37 4.502 kB 150.254.78.39 to previous | to last moved the parts irrelevant to Creole to the bottom
12 08-Feb-2007 00:42 3.659 kB 216.132.15.200 to previous | to last Egregious fussing
11 08-Feb-2007 00:40 3.664 kB 216.132.15.200 to previous | to last Needless fussing - JG^.^
10 08-Feb-2007 00:02 3.427 kB 216.132.15.200 to previous | to last Jim Gettman is a systems analyst for Point.360
9 05-Feb-2007 22:37 1.393 kB ChristophSauer to previous | to last romoved stuff since it is completely out of scope here... read before you post.
8 05-Feb-2007 19:51 6.89 kB 142.177.76.130 to previous | to last fixing the syntax suggestion as per Radomir (who should like this page now)
7 05-Feb-2007 19:21 6.932 kB 142.177.76.130 to previous | to last wiki best practices
6 05-Feb-2007 19:19 6.891 kB 142.177.76.130 to previous | to last a little more on tag/category coordination
5 05-Feb-2007 19:12 6.109 kB 142.177.76.130 to previous | to last fixing a few things, extending voting example
4 05-Feb-2007 19:04 5.546 kB 142.177.76.130 to previous | to last three examples, dunno this JSPwiki markup, hope I got it right
3 01-Feb-2007 16:50 1.393 kB RadomirDopieralski to previous | to last added some context
2 01-Feb-2007 14:12 0.165 kB ChristophSauer to previous | to last typo
1 01-Feb-2007 13:02 0.169 kB ChristophSauer to last
« This page (revision-20) was last changed on 04-Mär-2008 04:37 by 129.78.64.101