Beep beep. I, for example, hate the verbosity of html, but i use it
nevertheless. The popularity of Wikipedia made Media-Wiki syntax the
de-facto standard. It's not perfect, but please don't reinvent the
wheel (even though it's a PHP wheel).

It's funny - i was the first one who proposed the wiki idea and i
didn't think that it will go so far (1000$$$????). If you ask me, this
wiki should be done ASAP in Media-Wiki. Reusing current Perl wikis
(Australian, whatever) is even better. Perl6 currently needs
documentation, community and advocacy - not a Yet Another Content
Management System written in itself. It is unlikely that it will
become Perl6's killer app with such a strong competition.

As for CamelCase - it's long dead. Now, writing a Perl6 app to find
and exterminate [[random links]] would be neat (although it would
probably be a one-liner).

On 5/28/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote:
* Juerd <[EMAIL PROTECTED]> [2006-05-28 19:35]:
> - MediaWiki-compatible syntax

I hate the Mediawiki syntax. Can we have something that
understands blocks, like Markdown? Just add [[foo]] as intrawiki
link syntax.

>   - Most \W characters can be safely used

Yeah, that is true for Markdown.

>   - Package names (CamelCase) can be used without them being
>     transformed into links

I find CamelCaseLinking annoying as well. However, I do like how
it seems to gently guide people into picking NounsAsPageNames,
whereas random contributors tend [[to make really stupid]]
choices when given free-form links only. Good tools (page
renaming etc.) can help steer against that, but CamelCaseLinking
makes it less necessary to take corrective action in the first
place. However, it's also just plain damn ugly. :-/

Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>



--
Amir Elisha Aharoni, http://aharoni.blogspot.com/
"We're living in pieces,
I want to live in peace." - Thurston Moore
______________________________________________________
Please avoid sending me Word or PowerPoint attachments
http://www.gnu.org/philosophy/no-word-attachments.html

Reply via email to