discuss: Cheat sheet
Subject:
Re: Cheat sheet
From:
Randy Kramer ####@####.####
Date:
10 Apr 2001 20:55:00 -0000
Message-Id: <3AD372C2.6E80@fast.net>
Gary,
I decided to do a little searching in TWiki's developer's web and found
the links listed below. (I am a newbie to Perl, so I don't know whether
any of this fits your needs. There are other discussions about
converting the back end storage to a database instead of the plain text
files currently used.)
http://twiki.org/cgi-bin/view/Codev/PackageTWikiStore
http://twiki.org/cgi-bin/view/Codev/HowShouldTWikiBeModularized
http://twiki.org/cgi-bin/view/Codev/TWikiModularizationCvsBranch
I suspect you are not that interested, but my curiosity was piqued and I
wanted to try to reassess how things were progressing in this area.
Thanks for the discussion,
Randy Kramer
Gary Lawrence Murphy wrote:
>
> Well, authentication and version control kind of go counter to Wiki
> culture, so I've never needed them. The code I use has some degree
> of revision, but nothing so exacting as TWiki, ditto for authentication
> (one admin can lock a page). Wiki's are supposed to simple, and our
> company website is sitting on a server where all we get is PHP, no
> database, no RCS, just PHP (or perl).
>
> I'm not much of one for feature sets; I prefer to work from
> requirements, and for an open community resource where it is in the
> best interests of the community to keep it current and accurate,
> there's no requirement for version control or authorization beyond
> what can be done with simple whole-file backups; if someone hates you
> enough to vandelize your site, they are going to vandelize the RCS
> just as much as a simple page. I run three Wiki's (kernel, emacspeak
> and a fengshui wiki) and so far have had only positive experiences.
>
> What I _would_ like to find is an oo-perl implementation as that would
> be easier to integrate into the rest of our website; my constraints
> are that it must be plain perl as shipped in your average tar ball,
> and it cannot use any database other than perhaps gdbm. Why perl?
> Only because the PHP components of our site are from SIPS and SIPS is
> such spaghetti that it is virtually impossible to extend. For example,
> SIPS has a DMOZ-like directory (I've written a perl interface into
> this) and it would be useful if the wiki-powered pages could feed a
> search that could show relevent directory areas in the page footer.
> I'd also like to bring relevent RSS files into the margins.
>
> --
> Gary Lawrence Murphy ####@####.#### TeleDynamics Communications Inc
> Business Innovations Through Open Source Systems: http://www.teledyn.com
> "Computers are useless. They can only give you answers."(Pablo Picasso)
