(anonymous guest) (logged out)

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

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-19) was last changed on 26-Sep-2007 09:06 by ChuckSmith  

This page was created on 02-Feb-2007 02:39 by 62.252.32.15

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 15 changed one line
The problem is that users will not read specs. The will not read all the exceptions we put in like not allowing space after bullet, or that you have to close a heading with the excat number of equals signs you have at the beginning. People are learning the markup by trying out things. The will save and see what happens. They will maybe save again if it not works on the first try but thats it. If it still don't work they will tell you that markup sucks and all your hard developer work is in vain.
The problem is that users will not read specs. The will not read all the exceptions we put in like not allowing space after bullet, or that you have to close a heading with the excat number of equals signs you have at the beginning. People are learning the markup by trying out things. They will save and see what happens. They will maybe save again if it not works on the first try but thats it. If it still don't work they will tell you that markup sucks and all your hard developer work is in vain.
At line 93 changed one line
**The second option** is to use a very simple, even simplistic, totally rigid system, with very clear rules that can be observed from just a few common examples. This system must be totally predictable and open, so that everyone sees perfectly how it works. Ideally, you can say exactly what will happen by just looking at it -- in practice (in case of computers at least) this //is// dependet on prior experience, but we can assume the basic computer literacy for our users.
**The second option** is to use a very simple, even simplistic, totally rigid system, with very clear rules that can be observed from just a few common examples. This system must be totally predictable and open, so that everyone sees perfectly how it works. Ideally, you can say exactly what will happen by just looking at it -- in practice (in case of computers at least) this //is// dependent on prior experience, but we can assume the basic computer literacy for our users.
At line 101 added one line
I added a page called [[Ambiguities]] to document strategies on how to detect and solve those issues related to the stuff that forces us to make the machine (and the developer) work harder. I hope this helps us to sort out those problems better in the future.
At line 103 added 13 lines
-- ChristophSauer, 2007-02-08
In re- //...fail to see how they are relevant to Creole markup standard. I think they would be better directed at the browser and/or wiki wysiwyg editors developers. ... Would you feel bad if we removed your advices, at least the ones about interactive user interface?//
Yes, much of my edit was shamefully irrelevant to Creole, more of a rant against all the bad UI's I see.  I saw a place to add value, so I did, figuring subsequent wikians can pare the crap and polish the gems.  It was rude, really, because I didn't even read the discussion first.  The beauty of Wiki is that it preserves consensus, while blogs or discussion threads preserve disagreement.  //Ward Cunningham's Wiki digitally reverses the tragedy of the commons.//
//...I can see you're using rather unusual patter for the second-level bullet lists -- two asterisks seprated by a space. I've seen it only once before. Can I ask you where did you pick that up?//
As described for others, I didn't [[http://dictionary.reference.com/browse/RTFM|RTFM]] before editing, and didn't see a "cheat sheet" button, so I made that up on the spot because it conveyed the desired meaning.
I'm back to see the evolution of my input.  I joined, and am bookmarking wikicreole.
-- JimGettman, 2007-02-21
Version Date Modified Size Author Changes ... Change note
19 26-Sep-2007 09:06 13.708 kB ChuckSmith to previous restore
18 26-Sep-2007 01:02 13.721 kB 219.138.204.162 to previous | to last
17 24-Jul-2007 05:54 13.708 kB ChristophSauer to previous | to last The -> They
16 22-Feb-2007 02:47 13.707 kB JimGettman to previous | to last
15 22-Feb-2007 02:39 13.659 kB JimGettman to previous | to last
14 20-Feb-2007 16:32 12.405 kB ChristophSauer to previous | to last link to ambiguities
13 08-Feb-2007 21:51 12.113 kB RadomirDopieralski to previous | to last rantitty rantitty rant :)
12 08-Feb-2007 20:36 9.411 kB RaphLevien to previous | to last be clear, be consistent
11 08-Feb-2007 00:24 7.383 kB RadomirDopieralski to previous | to last welcome Jim Gettman
10 07-Feb-2007 19:59 6.238 kB SteffenSchramm to previous | to last
9 07-Feb-2007 15:49 5.565 kB RadomirDopieralski to previous | to last use cases?
8 07-Feb-2007 15:32 5.167 kB ChristophSauer to previous | to last spinning in cyrcles
7 07-Feb-2007 15:15 4.958 kB RadomirDopieralski to previous | to last no chances with worst case
6 07-Feb-2007 15:10 4.763 kB ChristophSauer to previous | to last not all people learn like this
5 07-Feb-2007 13:24 4.641 kB RadomirDopieralski to previous | to last small correction
4 07-Feb-2007 11:00 4.626 kB 150.254.78.35 to previous | to last make less work hard for more
3 07-Feb-2007 10:01 2.683 kB ChristophSauer to previous | to last how people learn
2 06-Feb-2007 22:42 2.142 kB SteffenSchramm to previous | to last
1 02-Feb-2007 02:39 0.296 kB 62.252.32.15 to last I agree
« This page (revision-19) was last changed on 26-Sep-2007 09:06 by ChuckSmith