Some patches..

"Mats Gefvert" <[email protected]> Sun, 3 Apr 2005 21:55:03 +0200
Newsgroups gmane.comp.php.cowiki.cvs
Message-ID <[email protected]>
Hi,

My name is Mats Gefvert and I downloaded CoWiki just last week to evaluate if we could use it as a company documentation system for everything from software documentation to meeting minutes etc, etc, and so far it looks really swell.

I'm probably going to make a company-wide demo in about a week, where we have to convince Upper Management that this is the thing to go for, and thus I needed to hack some quick changes to it to make it work the way we want it to. These changes include:

 * restricting a search to the current tree - because we're looking at putting a knowledgebase in there and we want to be able to search specifically in just that knowledgebase. Implemented as a simple checkbox with a title="" tag in the template, and just a simple $Criteria addition (tree_id = n, or something).

 * the user list is ordered by name, not by uid, which looks a lot nicer

 * only .php files are treated as plugins. the custom.PluginInfo plugin insisted on treating my .php.bak files as legitimate plugins

 * a new plugin: MarkupInfo, which displays a list of the most common markups (*...*, /.../ etc) in a list very similar in style to PluginInfo, which is displayed below the editor in the document editor. This is so our [ignorant] users can have a quick reference handy of how to write stuff.

 * MarkupInfo and PluginInfo are now collapsible in the templates, so you click on them to see the full list. It got a little crowded down there.

 * Swedish translation has been included

 * I fixed the PluginInfo module, which didn't treat \r\n nicely on Windows. But I think that was already fixed in the cvs version, I just happened to have the 0.3.4 release.

 * a bit of extra spacing included in the menus (between web sections). Just a pixel or two, made it look less compressed. We have a very sensitive graphics designer; she would have killed me.

 * I added a new markup, which I named //, simply. While inputing some texts, I found that - especially in lists or numbered lists - it was difficult to add extra line spaces, since that would break the numbering. So I found myself adding a lot of <br><br> tags, and suddenly I realized it would be nice if there was a shortcut for that, so I implemented // to give <br/><br/> in the xml file. After reading some recent texts in the mailing list, though, I realized // in particular was slightly less than brilliant and I may end up changing that to something else. But I think it's a nice feature.

I don't know if the "cvs" mailing list is the right place to ask, but I thought it looked the most applicable, so I'm just wondering if these things (some, or all of them) is something you would like to merge into your project?

Just a small note: I've been trying to make the changes as efficiently and carefully as possible, adhering to the coding standards as well as the template layouts as much as possible, so if you like my changes, it should be easy to merge them. I even included a little song in my MarkupInfo plugin, as that seemed to be the general custom :)

Regards,
Mats Gefvert