use Perl

• Twiki code (Score:2)

  by autarch (914)

  I looked at the Twiki code recently, and it's really scary. So scary I wouldn't even consider installing it.
  • Re:Twiki code (Score:1)

    by mako132 (2925)

    Nah. The install isn't a problem. It helps, however, to know how CGI work and the issues around the webserver owner and file permissions. The code may be scary, but it's been in use for a long time.
    • Re:Twiki code (Score:2)

      by autarch (914)

      My point wasn't that I thought the install would fail, but rather that the code was so disturbing that I would not be _willing_ to install it.
    • Re:Twiki code (Score:1)

      by jordan (120)

      I think I understand how CGI work and have a good handle webserver owner/file permission issues.
      

      The code might be ugly, I don't know, but I hear that CGI.pm is pretty frightening too, but I use it a lot.
      

      The fact that there's a huge user base, it's mature and actively developed mean a lot to me.
      

      Can anyone comment on how difficult it is to setup and maintain?
      • Re:Twiki code (Score:2)

        by lachoy (1663)

        Setup is fairly simple -- IIRC you just need to unpack the files into a directory, chown them if necessary, and point Apache to them. If you want HTTP auth then there's a file to edit in the /cgi-bin/twiki/ directory. Maintenance (in the programming sense) is basically zero. Taking care of content is far more time consuming.

        Modifying the look of it is somewhat of a pain. It doesn't use a modern templating system, which is more an indiciation of its age than anything else. It does have a facility called 'S
        • Re:Twiki code (Score:1)

          by jordan (120)

          • One nice thing about TWiki is the number of plugins. They're very easy to create as well: big plus.
            

          
          

          I would love to be able to integrate this knowledge-base/Wiki with the application we support for examples and tutorials. Plug-ins might be a big win.
          

          I'll try it out!
• CGI::Wiki (Score:1)

  by echo (2881)

  After a real quicky survey of existing modules I settled for CGI::Wiki to build a documentation wiki with. Its modular approach made it easy for me to customize it, integrating with the rest of the app's TT templates, adding diffs with Text:Diff. I found it easy to understand CGI::Wiki's source code.
• Wikis still take some getting used to (Score:1)

  by mako132 (2925)

  Only lately has our Wiki (Twiki) started to take off. For a while I was on the only one creating pages, but then slowly, a couple of people started and once I forced (instead of asked) my sys admins to use it, we're now rockin'. I'm finding that people find the Wiki syntax intimidating, just because it is different, even though it is simple. Also, some people aren't comfortable with the philosophy of a continuously modified document -- they want to do once, completely, and be done with it . So asking th
• Re: Wiki recommendations, anyone? (Score:2, Insightful)

  by jmcnamara (659)

  
  I recommend (and have recommended [perl.org]) CGI::Kwiki [cpan.org].
  • Re: Re: Wiki recommendations, anyone? (Score:1)

    by Louis_Wu (2993)

    If you want a completely unbiased [cpan.org] view of Wiki's, Ingy will be talking about Kwiki [kwiki.org] at the Seattle Perl Mongers [seattleperl.com] meeting on Tuesday night. Or you could check the SPUGWiki [perlocity.org] for more info.

    "So you want to talk about my modules [perl.org]?" (This talk has not been rated.)
    • Re: Re: Wiki recommendations, anyone? (Score:1)

      by jordan (120)

      Well, now, I'll have to look at CGI::Kwiki, too.
      

      Gosh, it looks so easy to try. why not?
      

      It looks like it's also pretty easy to extend. Thanks for the pointers.