Hi All I've just updated svn to support two new kinds of plugin: * post_delete called with node name, node id and version * post_moderate called with node name and node id (The only existing plugin point was post_write) Can anyone think of any other plugin points that might be useful? Nick
Nick Burch wrote:
Hi All
I've just updated svn to support two new kinds of plugin: * post_delete called with node name, node id and version * post_moderate called with node name and node id (The only existing plugin point was post_write)
Can anyone think of any other plugin points that might be useful?
Nick, Does this mean you've implemented my AutoPlugin idea? I'm quite excited :D. http://www.earth.li/pipermail/cgi-wiki-dev/2005q4/000226.html Also, we have an svn repository and people are updating it. Excellent! I notice Kake is still the owner of the module on CPAN, and no releases have happened. What changes are in the pipeline? What we really need is a Trac installation, or use the OG one, then we can view changesets and differences. Also we would be able to have tickets, milestones etc. Cheers, Ivor.
On Thu, 16 Mar 2006, IvorW wrote:
Does this mean you've implemented my AutoPlugin idea? I'm quite excited :D. http://www.earth.li/pipermail/cgi-wiki-dev/2005q4/000226.html
Not really. I just added a couple more hooks. Your idea looks interesting, but I think it'll be quite a bit of work still. We'd probably want to add in the pre_ plugin calls as a starter, and when that's working consider the auto stuff
Also, we have an svn repository and people are updating it. Excellent!
Yup. It's all part of Dom's evil scheme to take control of all the abandoned modules OpenGuides depends on
I notice Kake is still the owner of the module on CPAN, and no releases have happened. What changes are in the pipeline?
Dom will do the releases, once we're ready. Current changes in svn are: * not using the node name as the foreign key everywhere * moderation Grab the changes or readme from svn to see more The list of what I'm planning to do is at http://dev.openguides.org/wiki/NickBurch
What we really need is a Trac installation, or use the OG one, then we can view changesets and differences. Also we would be able to have tickets, milestones etc.
I was thinking about just using the openguides one for now, unless there's enough of a community seperate from og? Nick
On Thu, Mar 16, 2006 at 10:43:37PM +0000, Nick Burch wrote:
On Thu, 16 Mar 2006, IvorW wrote:
I notice Kake is still the owner of the module on CPAN, and no releases have happened. What changes are in the pipeline?
Dom will do the releases, once we're ready. Current changes in svn are: * not using the node name as the foreign key everywhere * moderation Grab the changes or readme from svn to see more
To clarify, I've spoken to Kake (on this list, even?) and she's given me co-maintainership on the CGI-Wiki modules.
The list of what I'm planning to do is at http://dev.openguides.org/wiki/NickBurch
What we really need is a Trac installation, or use the OG one, then we can view changesets and differences. Also we would be able to have tickets, milestones etc.
I was thinking about just using the openguides one for now, unless there's enough of a community seperate from og?
I plan to set up a separate trac instance for CGI::Wiki, largely because you can't integrate multiple SVN repos into a single instance AFAIK. But for now use the openguides one, yes. I also need to import the other CGI::Wiki modules into SVN at some point. This might be a good opportunity to implement the name change that was discussed a while ago and upload as Wiki::Toolkit instead? Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
On Thu, 16 Mar 2006, IvorW wrote:
Does this mean you've implemented my AutoPlugin idea? I'm quite excited :D. http://www.earth.li/pipermail/cgi-wiki-dev/2005q4/000226.html
OK, I've done a bit more, based on your idea. You can now have pre_retrieve and pre_write plugins. These are passed their parameters by reference (the other plugins get it by value), so you can tweak stuff before it gets into the normal retrieve/write code. There's no way yet for plugins to deny a read/write. Anyone got any thoughts on how this should be done, on both the plugin side (indicating a deny) and the Store side (what to return if a deny happens)? Dom - while I think, are you going to set up the Trac for cgi-wiki on urchin, or shall I sling it on a Torchbox server? Now, what's next on the cgi-wiki todo.... :) Nick
participants (3)
-
Dominic Hargreaves -
IvorW -
Nick Burch