(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 64 added 52 lines
Welcome Jim Gettman, thank you for your input. Feel free to add yourself to [[People]] if you wish.
I have several problems with the advices you posted -- in particular, I 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.
In particular, you talk about interactive behavior, preprocessing of the user input and design of data entry forms, etc. This has nothing to do with a text markup format. The only one of your advices that I can see directly applied to Creole is the last point, "Present data in the form optimal for the user's task.", which in case of Creole would be editing the page's text. Would you feel bad if we removed your advices, at least the ones about interactive user interface?
On an unrelated thing -- 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? I'm curious, and it could also help Creole (more experience is always better).
-- RadomirDopieralski, 2007-02-08
While I agree with the sentiment stated in the title of this page, I also feel it's a red herring. I don't hear anybody honestly concerned about the amount of CPU time required to parse Wiki markup. It's going to be negligible in any case, although of course it's always possible to bloat that by having layers of interpreted languages, etc.
I have two concerns that I feel "make the machine work harder" tends to sweep under the rug. Both affect usability directly.
First, complex rules can be **mysterious** and **confusing.** To use one current example, if a space is sometimes required after an asterisk to make a bullet, but other times not, that increases the chance that the user will get the unexpected behavior, and be confused. The gain from having simple rules, easily expressible (in the scope of this community) by things like regexes, is not to reduce the CPU time required for parsing, but to reduce user confusion.
Second, I think we need to work to make Creole as **consistent** as possible across wikis. That helps avoid breakage of markup as text is cut and pasted from one wiki to another, but, perhaps more importantly, avoids users having to carry around arcane rules about what works in one wiki but not another.
I realize that the goal of consistency is in conflict with ExtensibleByOmission (in the extreme, a demand for perfect consistency means that extension is impossible), but I think it's possible to keep both in mind and balance the two. I think it's realistic, and desirable, to expect that all "bread-and-butter" markup is consistent between Creole implementations. Low-probability corner cases such as improperly nested styling markup, as well as things that obviously //look// like extensions (cf. [[Crossmark]] macros) concern me quite a bit less. But, to carry the example further, if one wiki treats a line reading "*bullet" as a list item, and another does not, we guarantee misformatting when moving either text or users betweeen wikis.
-- [[Raph Levien]], 2007-02-08
There are generally two approaches to this:
**Option first** is to use various heuristics, "smart" code, maybe even guessing based on probabilities (that's how MSIE determines document encodings and mime type), bayesian networks (that's how most spam filters work) or evolving interfaces (adaptive menus, khe, khe). This approach seems to work very good in most common cases and go down in flames in the rarer ones. It works best if you have very narrow target audience with very well defined tasks. The two most common reactions this kind of techinque are: "Amazing, it's the first time I see something like that, how do they do it?" and "*beep* *beep* *beep* paper clip *beep* get *beep* out of my *beep* I *beep* hate it when this *beep* *beep* mother*beep* *beep* mechanical idiot knows better what I want to do!".
In general, it works miracles with one-time users that never expect to actually //know// the system and want to be guided by the hand. It prevents habituation and becoming the one who is actually in control. People //love// it in all kinds of information stands, interactive web pages created for entertainment, toys, educational programs, etc. People hate it in everything they view as tools, as means for some goal, not the goal itself.
**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.
While users generally tend to love or hate the things created with the first technique, they usually hardly have any emotional attachment to the second kind. They usually won't even notice them. They will be surprised that you pointed out the mere existence of these elements. "Yeah, it's there, isn't it obvious?" However, you tend to notice the lack of them. These //tools// are usually intimidating or even scary for first-time users, but allow really fast learning and habituation, provided that discoverability of the interface is accounted for. Ah, and they also encourage extending and building more complex things on top of them.
While both approaches have their advantages, especially the first one guarantees easy adoption and allows for a very good branding compaign (love/hate is good for advertising), I strongly believe we should lean for the second option, as "the right thing" for a standard.
-- RadomirDopieralski, 2007-02-08
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.
-- 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