(anonymous guest) (logged out)

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

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 
This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

This page is reserved for discussion about implementation of Creole in TikiWiki. The item is on our wishlist. There is no set date at the moment.

My (marclaporte) impression: I am very pleased and impressed by the huge amount of research, work and thought put into picking each syntax for Creole. I much appreciate reading the various reasoning pages. Many things are the same or very similar to TikiWiki. For the things that are different, I sometimes feel the Creole way is better. For some other things, I need to think about it a bit more :-)

I think that a common syntax goes beyond wikis. It should be for all Web applications, cell phones, PDAs, accessibility, etc. Some desktop mail applications such as Thunderbird handle some sort of wiki syntax as well. Please see: http://dev.tikiwiki.org/Why+Wiki+Syntax+is+Important

  1. Interesting syntax: Double square brackets for external links is better in Creole than the current single brackets used by Tiki (accidental linking currently happens as described at LinksReasoning). Note: The current wiki also has the same issue. See the link to implementation at the top.
  2. is nice for italic, so is for underscore
  3. Some of the syntax (bold vs underscore, box vs superscript) would conflict but nothing catastrophic at first glance.
  4. Creole has some interesting Additions as well.

Things to consider:

  1. Some of the wiki engines support Creole by offering an optional plugin/extension which needs to be installed separately. Since most software users don't change the default, this hinders progress of Wiki Creole. Tiki applies the Wiki Way to software development and the convergence/collaboration culture is very strong. The Tiki community doesn't have the culture of an optional plugin/module/extension system which you pick and choose from several different similar features/options. More on this at http://marclaporte.com/TikiSucks If we go along with this, very likely, it'll be in the main code base, installed by default.
  2. Current install base is in the tens of thousands so we need a smooth migration path (data and UI). We could add some of the syntax which doesn't conflict and promote those until we eventually phase out the old way.
  3. Tiki is not just a wiki, but also a forum, blog, file gallery, calendar, etc. so we have internal links vs external links and we have a syntax to reuse content in the wiki (ex.: upcoming 10 events, last 10 articles). We must also make sure of no bad side effects with short URLS (reWrite Rules). Ex.: /forums is not the wiki page forums but the list of forums.
  4. It would be nice to simplify the current TikiWiki plugin syntax
  5. Tiki parser is rock-solid and hasn't significantly been changed for years. Any change could have unintended side effects.
  6. The most popular wiki is MediaWiki. In a perfect world, MediaWiki (and all the wiki engines) would adopt Creole and the millions of MediaWiki-formatted pages become more accessible. As discussed with Evan, this could be very difficult to do. Until then, as many people are migrating from MediaWiki to TikiWiki when they need more features so the work on Creole must not conflict. What is the official word on Creole support by MediaWiki?

Related:

Add new attachment

Only authorized users are allowed to upload new attachments.

« This particular version was published on 02-Jun-2008 17:14 by MarcLaporte.