SourceForge.net Logo
April 13, 2006
© GPL
 
ProWikiCenter
Automatic Linking /
Pro And Con

 
Difference (previous author) (Change, Edit, normal page display)

Changed: 5c5
Incorrect spelling. This is a Wikipedia arguement. AutomaticLinking, like e. g. CamelCase is incorrect spelling. In an official text - a dictionary, an encyclopedia - you will want to avoid incorrect spelling and at least CamelCase.
Incorrect spelling. This is a Wikipedia argument. AutomaticLinking, like e. g. CamelCase is incorrect spelling. In an official text - a dictionary, an encyclopedia - you will want to avoid incorrect spelling and at least CamelCase.

Changed: 9c9
Unwanted links. Sometimes with AutomaticLinking people write an article only to find that there appeared a lot of links that they didn't intend to put in. This can be annoying. It can be additional work to suppress these links by special Markups or Options.
Unwanted links. Sometimes with AutomaticLinking people write an article only to find that a number of links appear that they hadn't intended. This can be annoying for some authors. It can then be additional work to suppress these links by special Markups or Options.

Changed: 11c11
: ProWiki offers: Markup/Nowiki, Option/LinkSuppress.
: ProWiki offers: Markup/Nowiki, Option/LinkSuppress, HowTo/TurnAutomaticLinkingOff.

Changed: 15c15
Less work. AutomaticLinking is typically the same work as typing normal text, while ExplicitLinking adds additional commands or at least command characters. So AutomaticLinking is less work and more fun.
Less work. AutomaticLinking typically needs exactly the same number of key-strokes as typing normal text, while ExplicitLinking forces the user to type additional commands. Therefore AutomaticLinking is less work and more fun.

Changed: 17c17
Pattern language. Many communities are learning communities, so called CommunitiesOfPractice, working to understand and solve problems of a specific domain. This naturally results in a PatternLanguage that is best represented in CamelCase.
Pattern language. Many communities are learning communities, so called CommunitiesOfPractice, working to understand and solve problems of a specific domain. This naturally results in a PatternLanguage that is best represented by using CamelCase.

Changed: 19c19
Incidental linking. Often people find that AutomaticLinking forms unexpected but fruitful links that help to organize the wiki chaos and make the pieces of the puzzle fit together.
Incidental linking. Often people find that AutomaticLinking forms unexpected but fruitful links that help to organize the WikiChaos and make the pieces of the puzzle fit together.

These are arguments pro and contra AutomaticLinking.

Contra

Incorrect spelling. This is a Wikipedia argument. AutomaticLinking, like e. g. CamelCase is incorrect spelling. In an official text - a dictionary, an encyclopedia - you will want to avoid incorrect spelling and at least CamelCase.

ProWiki offers an compromise: UnderlineLinking.

Unwanted links. Sometimes with AutomaticLinking people write an article only to find that a number of links appear that they hadn't intended. This can be annoying for some authors. It can then be additional work to suppress these links by special Markups or Options.

ProWiki offers: Markup/Nowiki, Option/LinkSuppress, HowTo/TurnAutomaticLinkingOff.

Pro

Less work. AutomaticLinking typically needs exactly the same number of key-strokes as typing normal text, while ExplicitLinking forces the user to type additional commands. Therefore AutomaticLinking is less work and more fun.

Pattern language. Many communities are learning communities, so called CommunitiesOfPractice, working to understand and solve problems of a specific domain. This naturally results in a PatternLanguage that is best represented by using CamelCase.

Incidental linking. Often people find that AutomaticLinking forms unexpected but fruitful links that help to organize the WikiChaos and make the pieces of the puzzle fit together.


FolderArguments