September 2003 - CGI-Wiki-dev

Re: [cgi-wiki-dev] Convergence with Kwiki?
by Tom Insam 14 Sep '03

14 Sep '03

At 0:34 -0400 2003/09/14, <Martin(a)Cleaver.org> wrote: >Hi Kake, >More questions has anyone proposed, and what's >the general feeling about, merging the efforts >of CGI::Wiki and Kwiki? I question the need for >independent efforts and wonder whether a joint >community would have better economies of scale. >Cheers, > Martin Apart form Jonathan's point, for me the main difference is that Kwiki is a bit of CGI that implements a Wiki. CGI::Wiki isn't, it's a toolkit that lets you build a wiki. There's an important difference - to change how Kwiki works, you're removing bits of it and doing your own thing. You don't need to change how a CGI::Wiki engine works, hopefully, it's just a matter of building the front end differently. Of course, having said that, I _did_ write CGI::Wiki::Kwiki, which was intended to be a simple Kwiki-like front end to CGI::Wiki that Just Worked, but that was more of a 'move your kwiki to a 'real' database' aid than anything else. There's no way that openguides could have been built on a Kwiki without serious messing around. Openguides is obviously a wiki, but not what I'd think of as a 'traditional' wiki... -- .tom

3 2

Mailing list vs wiki for discussion
by Martin＠Cleaver.org 14 Sep '03

14 Sep '03

Just for the record I will say that I prefer a wiki for discussion to email. I like being able to refactor and cross reference for other people and to use pages to build consensus of opinion. And that's without cluttering my mailbox. I do recognise that this only works well on TWiki because that retains page histories - am I right in thinking that this is not the case for CGI::Wiki? Cheers, Martin ------Original Message----- =From: Kate L Pugh [mailto:kake@earth.li] =Sent: Wednesday, 3 September 2003 4:03 AM =To: Martin(a)Cleaver.org =Subject: Re: Text file backend? = =On Sun 31 Aug 2003, Martin(a)Cleaver.org wrote: => 1 Is there a wiki used for discussing CGI::Wiki? I'm thinking =something => along the lines of http://www.twiki.org/cgi-bin/changes/Codev. There are => some others that I'd like to bring into the conversation but obviously =I'm => keen to avoid the limitations of email. = =I don't really like wikis for discussion. I've set up a mailman list =which you can subscribe to at = http://www.earth.li/cgi-bin/mailman/listinfo/cgi-wiki-dev = => 2 What's the best demo site for CGI::Wiki? = =Probably the main OpenGuides one - http://openguides.org/london/ =The OpenGuides code is on CPAN. = =Kake

1 0

making nodes first-class objects
by Jonathan Swartz 11 Sep '03

11 Sep '03

Hi all, A few days ago I started a conversation with Kake about one unsatisfying aspect of CGI::Wiki's API: that the object-orientedness is not extended to nodes and other concepts in the system. Returning nodes as hashes exposes the internal elements of your implementation, makes it harder for folks to extend nodes via subclasses, and just feels wrong in today's object-oriented world. I'd love to see CGI::Wiki::Node as a first class object. Then, * content(), last_modified(), metadata(), etc. are accessor/mutator methods on CGI::Wiki::Node (zero arguments gets the value, one argument sets the value) * verify_checksum() and delete() are methods on CGI::Wiki::Node * retrieve_node() returns an CGI::Wiki::Node object (or undef if it doesn't exist - it is bad form to assume an empty node, IMO) * list_backlinks(), list_dangling_links(), etc. return a list of CGI::Wiki::Node objects There are some nice utility classes that can help construct the CGI::Wiki::Node class, like Class::Accessor and Class::DBI. Obviously for backwards compatibility we'd want to keep both APIs around for a while. Kake suggested that we use an api_version parameter in the constructor: my $wiki = CGI::Wiki->new( api_version => 2, # 1 is hash-based, 2 is object-based ..., ); What do people think? Jon

3 5

Re: [OpenGuides-London] Openguides london error message
by Kate L Pugh 11 Sep '03

11 Sep '03

On Wed 03 Sep 2003, Billy Abbott <billy(a)cowfish.org.uk> wrote: > just got this error when trying to add a new entry, > > Search::InvertedIndex::update() - Failed to save updated > 'ged_000000000000_a_000000000972' -> (list of ranked keys) at > /home/earle/openguides.org/lib/CGI/Wiki/Search/SII.pm line 204 I've had this one before. There is *something* up with Search::InvertedIndex but for the life of me I know not what. The author of Search::InvertedIndex is a very nice person but is too busy to spend much time on it. Does this scratch anyone's itch? I have some code from him that is more recent than the latest CPAN version, plus a reworking of the docs that I did to make them more understandable. Give me a shout if Search::InvertedIndex is something that you'd like to play with. Kake

1 0

Wiki zen garden
by Kate L Pugh 04 Sep '03

04 Sep '03

[cced to OpenGuides and CGI::Wiki dev lists - Matt, please feel free to join either or both of these. URLs at bottom of mail.] Hi Matt, Paul Mison pointed me at your post about wikis: http://a.wholelottanothing.org/archives.blah/007391 Sounds like you might be interested in some stuff I've been writing. CGI::Wiki is a perl distribution (available on CPAN) that provides a backend for wikis and wiki-like applications. Despite the name, it does no CGI whatsoever - it just stores, indexes and retrieves content and metadata.

1 0

test
by Kate L Pugh 03 Sep '03

03 Sep '03

Just a test, no need to reply.

1 0