First, I'm enthusiastic and honored that there has been a good bit of interest. I appreciate all of the feedback thus far. Please keep them coming. Also of note…
Rael Dornfest released a beta of version 2 of his weblogging tool Blosxom (he's up to Beta 3 now) that adds plugin capabilities. One example plugin included a TikiText plugin. Excellent!
Rael also has been thinking about the crossover between Wikis and weblogs that and is experimenting using my TikiText module. (An interesting thought. More on this later.)
DJ Adams has fused Text::Tiki into his favorite Wiki tool MoinMoin concluding the 'natural environment' for a wiki-like markup language is ... in a Wiki.
Very interesting. It certainly puts a few thoughts in my head to ponder.
Since TikiText has gone into regular use with some, I'm releasing a maintenance release to plug a few holes that have been discover in the TikiText processing engine. From the change log:
- fixed bugged where formatting immediately in () and {} was not recognized.
- fixed improper coding of anchor targets. (Paul Holbrook)
Download: .ZIP | .GZ | Reference Guide 0.17
I've been at work on the next major release of the engine with whatever bits of free time I salvage from my day. (I'm beginning to sound like Rael.) Here are a few highlights. First the bad news.
- The symbol of CODE blocks will be changing.
-
I had a mental lapse here and should not have used the | (pipe) character since I knew table support was needed and the pipe is almost universally applied to that. Since I did say this was experimental I only feel a little bit bad about this. So let me clarify previous statements: this module/implementation is in beta, but the syntax is an alpha. (Does that make sense?)
-
I think the greater good is that Tiki supports tables that are similar to previous exsisting conventions then do something totall different and counter-intuitive. Hopefully you agree.
- Lists in <blockquote>s. Nested <blockquote>s. etc.
-
I'm working on substantially refactoring the code to support nesting of elements better. I'm pretty sure the code coude shirk a bit and some minor performance gains achieved. We'll see.
- Implement <image>
-
will be used to insert an image. The engine will automatically calculate the height and width.
- Implement <tables>
-
Basic Wiki-style tables will be implemented in some form. The table will be of a similar style to Twiki however I'm considering using a symbol just inside the cell, denoted by a | (pipe), so I ignore leading and trailing whitespace in each cell. My reason is that authors should have the option to make tables readable without being parser – assuming they are using a fixed-width font.
- Implement callback for WikiWords
-
While TikiText undeniable descends from Wiki notation, it was never my intention to replace it or have TikiText put into that use. There seems to be interested based on Rael and DJ's experience. Being one to please I will be adding a callback hook to Text::Tiki for those who are implementing this module in ways where this would be useful. WikiWord support will be completely optional. A WikiWord link is an implementation issue that varies and in some cases may not be warranted at all.
I've updated the TO DO section of the documentation accordingly. The TikiText Forum is still open here your comments and suggestions are welcomed.
<p>First, I'm enthusiastic and honored that there has been a good bit of interest. I appreciate all of <a href="http://www.timaoutloud.org/projects/tiki/beta.html">the feedback thus far</a>. Please keep them coming. Also of note…</p>
<p>Rael Dornfest released <a href="http://www.raelity.org/archives/computers/internet/weblogs/blosxom/blosxom_2_0_b1.html">a beta of version 2 of his weblogging tool Blosxom</a> (he's up to <a href="http://www.raelity.org/archives/computers/internet/weblogs/blosxom/blosxom_2_0_b3.html">Beta 3</a> now) that adds plugin capabilities. One example plugin included a <a href="http://www.raelity.org/archives/computers/internet/weblogs/blosxom/plugins/tiki.html">TikiText plugin</a>. Excellent!</p>
<p>Rael also has been thinking about <a href="http://www.raelity.org/archives/computers/internet/weblogs/blosxom/plugins/wikiwordish.html">the crossover between Wikis and weblogs</a> that and is experimenting using my TikiText module. (An interesting thought. More on this later.)</p>
<p>DJ Adams has <a href="http://www.pipetree.com/qmacro/2003/02/22#tikiparser">fused Text::Tiki into his favorite Wiki</a> tool <a href="http://moin.sourceforge.net">MoinMoin</a> concluding <q>the 'natural environment' for a wiki-like markup language is ... in a Wiki.</q> Very interesting. It certainly puts a few thoughts in my head to ponder.</p>
<p>Since TikiText has gone into regular use with some, I'm releasing a maintenance release to plug a few holes that have been discover in the TikiText processing engine. From the change log:</p>
<ul>
<li>fixed bugged where formatting immediately in () and {} was not recognized.</li>
<li>fixed improper coding of anchor targets. (Paul Holbrook)</li>
</ul>
<p>Download: <a href="http://www.timaoutloud.org/projects/tiki/tiki.zip">.ZIP</a> | <a href="http://www.timaoutloud.org/projects/tiki/tiki.tar.gz">.GZ</a> | <a href="http://www.timaoutloud.org/projects/tiki/docs017.html">Reference Guide 0.17</a></p>
<p>I've been at work on the next major release of the engine with whatever bits of free time I salvage from my day. (I'm beginning to sound like Rael.) Here are a few highlights. First the bad news.</p>
<dl>
<dt>The symbol of CODE blocks will be changing.</dt>
<dd>
<p>I had a mental lapse here and should not have used the | (pipe) character since I knew table support was needed and the pipe is almost universally applied to that. Since I did say this was experimental I only feel a little bit bad about this. So let me clarify previous statements: this module/implementation is in beta, but the syntax is an alpha. (Does that make sense?)</p>
</dd>
<dd>
<p>I think the greater good is that Tiki supports tables that are similar to previous exsisting conventions then do something totall different and counter-intuitive. Hopefully you agree.</p>
</dd>
</dl>
<dl>
<dt>Lists in <blockquote>s. Nested <blockquote>s. etc.</dt>
<dd>
<p>I'm working on substantially refactoring the code to support nesting of elements better. I'm pretty sure the code coude shirk a bit and some minor performance gains achieved. We'll see.</p>
</dd>
</dl>
<dl>
<dt>Implement <image></dt>
<dd>
<p><img src="IMG-URL" alt="alt-text"/> will be used to insert an image. The engine will automatically calculate the height and width.</p>
</dd>
</dl>
<dl>
<dt>Implement <tables></dt>
<dd>
<p>Basic Wiki-style tables will be implemented in some form. The table will be of a similar style to <a href="http://twiki.org/cgi-bin/view/TWiki/TextFormattingRules">Twiki</a> however I'm considering using a symbol just inside the cell, denoted by a | (pipe), so I ignore leading and trailing whitespace in each cell. My reason is that authors should have the option to make tables readable without being parser – assuming they are using a fixed-width font.</p>
</dd>
</dl>
<dl>
<dt>Implement callback for WikiWords</dt>
<dd>
<p>While TikiText undeniable descends from Wiki notation, it was never my intention to replace it or have TikiText put into that use. There seems to be interested based on Rael and DJ's experience. Being one to please I will be adding a callback hook to Text::Tiki for those who are implementing this module in ways where this would be useful. <strong>WikiWord support will be <em>completely</em> optional.</strong> A WikiWord link is an implementation issue that varies and in some cases may not be warranted at all.</p>
</dd>
</dl>
<p>I've updated the TO DO section of the documentation accordingly. The TikiText Forum is still open <a href="http://www.timaoutloud.org/projects/tiki/beta.html">here</a> your comments and suggestions are welcomed.</p>

Leave a comment