On 03 Apr 21:55, Mats Gefvert wrote:
Hi again Mats,
> 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 hope you mean 'well' :-)
> 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).
How exactly does it look like? Visually? Makes it sense (or is it
continuous) for a normal user with a normal coWiki installation?
> * the user list is ordered by name, not by uid, which looks a lot nicer
Its a good idea to extend this plugin by parameters that can steer such
behaviours. Additional parameters are easy to implement, but we should talk
about them first on e.g. the dev- or issues- lists. Your precise suggestions
are welcome - better code suggestions :)
> * only .php files are treated as plugins. the custom.PluginInfo plugin
> * insisted on treating my .php.bak files as legitimate plugins
We ran into it too recently, this bug has been fixed in the CVS meanwhile.
> * 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.
This is an awkward point. We are (re)working the parser at this time. I am
sure that a plugin that describes how the coWiki syntax works will be
irritating for you users at least for the next version of coWiki - or you
will have an old description with a new behaviour or such. It would be
better for your users to refer to the online documentation, e.g. like at
<http://cowiki.org/131.html>.
> * 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.
I see. We didn't talk about the use of JavaScript for coWiki yet since the
new maintainer took over the project over. And I suppose you use JavaScript
or at least CSS to achieve this. This is also a behaviour, we would need
talk about at the dev- list.
> * Swedish translation has been included
If you want to care about the Swedish translation also in the future, you
are warmly welcome :)
> * 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.
I am not sure, but this might be also be fixed in the latest CVS
(<http://cowiki.tigris.org/issues/show_bug.cgi?id=107>). Anyone an idea?
> * 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.
Well, this is your template and I don't think that we want more templates at
this time, because it is error prone to fix small things x-times in different
templates. Use and change your template as you wish.
> * 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 am bored to talk about markup, maybe others want to talk about it. And
please see the parser-rewrite issue that I mentionen above.
> 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?
I think I can speak for the Paul, the project owner and maintainer, that we
are very interested in people who want to contribute to coWiki. The
difficulity is "what" and "how". You have a bunch of changes, so we'll need
to listen to Paul and his management ideas. :)
> 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 :)
A song? Uh? I thought, I have sometime one beer too much on weekends ... :)
regards dtg
|
