CGI-Wiki-dev

cgi-wiki-dev@earth.li

134 discussions

Testing schema upgrade 9->10: help wanted!
by Dominic Hargreaves 22 Jun '08

22 Jun '08

Current subversion of Wiki::Toolkit includes my proposed schema 10 version changes. The changes themselves aren't large, but I've also rearranged code to enable unit testing of schema upgrades. This ought to mean that there's less of a need to hassle people to try upgrades, but nonetheless I'd be grateful if people could test the upgrade to the SVN version (backup your database, or do the test on a development snapshot of your database!) Let me know which database you've run the test on and whether you ran into any problems. I would like to release a version with this schema ASAP (this weekend hopefully) in order to catch the freeze of library packages for Debian. Thanks, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

2 4

Schema update in subversion
by Dominic Hargreaves 26 May '08

26 May '08

Just a note to point out that I've committed schema changes for version 10; however, I think I will need to make updates to this schema when I come back from holiday in over a week, so in the meantime please don't use this code on production databases (like you'd do that..!) Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

1 0

Recent Changes addition - finding new pages
by Kake L Pugh 12 May '08

12 May '08

I've just added the "new_only" parameter to ->list_recent_changes, to let you ask for e.g. all pages added in the last week (as opposed to all pages edited in the past week). This involved a bit of a rewrite of ->list_recent_changes, and I'm not convinced that the test suite covered everything that it should have, so I may have introduced bugs. This change is in svn. I'd really appreciate it if people could check the svn versions out and run the tests, particularly if you have multiple backends to test on (SQLite, PostgreSQL, MySQL, Plucene, Search::InvertedIndex, etc). svn co https://urchin.earth.li/svn/wiki-toolkit/wiki-toolkit/trunk Kake

2 6

How to write node with versions
by abhishek jain 09 Jan '08

09 Jan '08

Hi, I do intend to create a wiki using Wiki::Toolkit . I am having problems writing nodes with versions, i mean i can create node but i am not able to update the content of the node, Can anyone here suggest me pl. Also i am short of concepts of wiki, if i am not wrong: 1. node = a unique html page dedicated to a title Any help soon will be appreciated. -- Thanks and kind Regards, Abhishek jain

5 13

How does Backlink works
by abhishek jain 28 Dec '07

28 Dec '07

Hi, Thanks for the previous replied to my previous question. It did worked. Now i am having problem understanding how backlink list_backlinks function works, i mean what i have to write in page for the code to automatically detect it as a link and that this link links to this particular node. Also i am using formatter as UseMod and am finding it is replacing eg. < with the > i mean it should not replace it i want to display HTML and not the character < or > . Waiting for your response , -- Thanks and kind Regards, Abhishek jain

2 1

Evaluating Wiki Toolkit
by Robert Barta 17 Sep '07

17 Sep '07

Hi folks, I am just looking at Wiki::Toolkit and it's plugin infrastructure. I read in http://search.cpan.org/dist/Wiki-Toolkit/lib/Wiki/Toolkit/Plugin.pm that pre_retrieve does not allow declining of the read. It is marked as TODO. Is there a principle problem with it? or could it be added, just as for instance in sub write_node_post_locking { .... foreach my $plugin (@preplugins) { if ( $plugin->can( "pre_write" ) ) { handle_pre_plugin_ret( \$write_allowed, $plugin->pre_write( node => \$node, content => \$content, metadata => \$metadata_ref ) ); } } if($write_allowed < 1) { # The plugins didn't want to allow this action return -1; } ?? \rho

3 3

Universal wiki edit button
by Earle Martin 04 Jul '07

04 Jul '07

Hi all, One of the things that people talked about during the RoCoCoCamp conference (http://rocococamp.info/) back in May was creating a recognisable visual identity for the "edit this page" button, much as how the orange "waves" symbol now represents RSS feeds in many browsers. There's been a bunch of brainstorming over possible icons (http://www.aboutus.org/UniversalWikiEditButton/IconIdeas) and one's been settled on as "good enough for version 0.1". Your comments are most welcome at http://www.aboutus.org/UniversalWikiEditButton. Would people be amenable to including "the button", whatever it ends up as, in a forthcoming Wiki::Toolkit release? Cheers, Earle. -- Earle Martin http://downlode.org/ http://purl.org/net/earlemartin/

2 1

Fwd: [wiki-standards] WikiCreole 1.0 Press Release
by Earle Martin 04 Jul '07

04 Jul '07

---------- Forwarded message ---------- From: Chuck Smith <csmith(a)hs-heilbronn.de> Date: 04-Jul-2007 13:00 Subject: [wiki-standards] WikiCreole 1.0 Press Release To: Discussion of wiki research and practice <wiki-research(a)wikisym.org>, The discussion list for wiki standards <wiki-standards(a)wikisym.org> Link to this press release: http://www.wikicreole.org/wiki/WikiCreolePressRelease To digg it: http://digg.com/software/WikiCreole_1_0_a_common_wiki_markup FOR IMMEDIATE RELEASE After a year of diligent effort, a group of nearly 50 dedicated users and developers are proud to release WikiCreole 1.0. Creole is designed to be a common wiki markup language which augments existing markup to enable wiki users to transfer content seamlessly across wikis, a boon to novice and expert users alike. Creole, taking its name from the field of linguistics, a stable language that originated from a combination of two or more languages. As every wiki software has its own markup definitions, the differences can make them difficult for novices to learn and experts to remember, thus a common wiki markup lays the foundation for development of cross-engine wiki software. The Creole name for a common markup was born from an idea of wiki founder Ward Cunningham at Wikimania 2006 the international Wikipedia conference. The goal: create a common markup that was not a standardization of an arbitrary existing markup, but rather a new markup language that was created out of the common elements of all existing engines. Under this premise the Wiki Creole Working Group analyzed existing wiki markup and compiled a greatest-common denominator subset of elements and presented its report. Practitioners and wiki developers were then invited to a workshop at WikiSym 2006 in Denmark to learn about Creole and discuss how to proceed. WikiSym is a symposium (conference) series dedicated to wiki research and practice. Participants evaluated different markup elements for possible unification and added them to a wiki created for this purpose. The resulting data resulted in the first version of the Creole spec, version 0.1. Many workshop participants also agreed to implement Creole into their existing wiki implementations. In true wiki fashion, the report and data were published to a wider audience who were unable to attend allowing them to discuss the decisions made and add their own proposals. An iterative workflow was introduced that discussed and introduced these new proposals into the spec. Discussion pages were used to address each topic and at the end of each iteration (4-8 weeks), a new version number was added to the spec. The working group's goal was to emphasize consensus instead of majority rule, so opinion polls were always followed by an attempt to reach mutual agreement. After many long months of cooperation, the working group finally reached a point of maximum commonalities. Creole 1.0 was then frozen for the next two years to allow time for adoption. The WikiCreole site (www.wikicreole.org) now has extensive documentation of the empirical analysis and discussions of the elements to support the decisions behind the spec. Today, ten wiki engines support Creole and many more are planning to implement it in the coming months. Wiki engine developers implementing WikiCreole in their parsers, give a clear sign to the community of their readiness to cooperate and draw us all closer together, making life easier for everyone in the wiki world. With the support of i3G (Interdisciplinary Institute for Intelligent Business Processes; Heilbronn, Germany), Christoph Sauer and Chuck Smith have led the process with great help from the wiki developer community through its initial concept to 1.0. Through their selection of content and personnel, i3G, is trying to overcome the barriers between computer science, engineering and business. They also develop customized concepts for companies to help optimize operational workflow and its representation for IT systems. For more details, contact Chuck Smith at +49 7131 504 474 or csmith(at)hs-heilbronn.de _______________________________________________ wiki-standards mailing list. wiki-standards(a)wikisym.org http://www.wikisym.org/cgi-bin/mailman/listinfo/wiki-standards For the wiki-research, wiki-standards, wikisym-announce mailing lists, please see: http://www.wikisym.org/cgi-bin/mailman/listinfo -- Earle Martin http://downlode.org/ http://purl.org/net/earlemartin/

1 0

Review date field
by Dominic Hargreaves 19 Jun '07

19 Jun '07

OpenGuides has had a long-standing feature request from me which I'm now thinking about implementing: http://dev.openguides.org/ticket/1 The idea would be to prevent entries from getting too stale by storing some meaningful data about when the node was last checked over for accuracy (as opposed to other minor changes). This could be done a couple of ways: - as per http://london.randomness.org.uk/wiki.cgi?Trinity%2C_SW4_0JG in free-text in the node content With a ticky-box: "If you have verified the content of this article as correct, please ticky ticky [ ]" Suggested rendering of this data - at the bottom of pages: "This page was last checked for accuracy on yyyy-mm-dd" This itself could be done two ways: - as Wiki::Toolkit metadata - automatically populate it with a standard string representation of the date if appropriate The way I'm starting to favour, though, is a new sort of Wiki::Toolkit data. This has the advantage that it can be typed correctly (as a date object). It's a bit more work to implement, but not too much. The question is, whether this is an appropriate addition to Wiki::Toolkit. Since it is in many ways similar to the modified stamp, I think it is. The question also arises of whether we could also use a "should be reviewed on the following date" - ie an explicitly staleness factor, rather than just inferring such (6 months after last reviewed date, for example). Would it be overkill to be able to specify both? Kake is in favour of retaining free text descriptions (useful of only some parts of the content have been verified) but this doesn't allow systematic searches on this data (so we can proactively go out and regularly review nodes, for example. There's no reason, of course, that we can't keep both functions - people can carry on doing this even if there is more structured data available too. Or we could add a separate free text field, as a normal metadata field. Any opinions welcomed. Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)

1 0

Wiki developers' IRC meeting tonight, 8pm UTC
by Earle Martin 06 Jun '07

06 Jun '07

Hi all, You may be interested in attending the first occurrence of the new monthly wiki developers' meeting, in #wikiohana on irc.freenode.net, at 8pm UTC tonight. The agenda is at http://wikiohana.net/cgi-bin/wiki.pl/IrcMeetingJune2007 ; I think discussion will be mainly about the WikiCreole (http://wikicreole.org/), a proposed common format for wiki markup. It would be really cool if Wiki::Toolkit could support it in some fashion later down the line; and of course your feedback about the whole idea would be very welcome. Cheers, Earle. -- Earle Martin http://downlode.org/ http://purl.org/net/earlemartin/

4 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

CGI-Wiki-dev