Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by Matts (1087) on 2003.01.06 6:50 (#15782) Journal
    Yes, I think wiki's are pretty sexy. The reason I've got completely separate Wiki modules is that Text::WikiFormat is slightly designed to allow overriding the output, but it doesn't go far enough. It's still very much designed to take Wiki text as a string and output a string. If on the other hand you adopted the SAX model, your input can be a string, a file or a filehandle, and the output is a data format (which you can then turn into a string or HTML if you so wish). I need that flexibility to be able to properly process Wiki text as XML in the AxKit Wiki.

    The other thing about the AxKit wiki is that you can author pages in POD, which I find very sexy indeed. POD isn't the world's best format, but it's actually really well suited to Wikis.

    (I concur with the database update issue - it's a complex problem that I've never seen solved perfectly).
    • Matts wrote:

      The other thing about the AxKit wiki is that you can author pages in POD, which I find very sexy indeed. POD isn't the world's best format, but it's actually really well suited to Wikis.

      Now look what you made me do [penseroso.com].

      I must look into AxKit at some point. I seem to have the idea that it'll all be too complicated for me to grasp, though this may or may not have any relation to reality.