Posted by sorenp on February 27, 2007 at 12:15pm
I just stumbled over rötiz Wikitools module and couldn't help noting that all features listed, except for "Node Search" and Freelinking integration are already supported by Liquid (*). I do in general welcome new approaches and I'm glad to see that more developers team up around the drupal wiki consept, but what is there a point in running two separate races for the same goal?
Best Regards,
Soren
(*) Node Search and Freelinking support has been implemented as a separate addon modules that will be distributed with the next version of Liquid
Comments
why wikitools
The reasoning behind wikitools was:
1. A simple module which does not use additional database tables.
2. All options can be set according to the site's needs (for example I have a site where 'move protection' or 'unique titles' is not necessary).
3. The whole site is accessible to wikilinks.
4. Integration with existing input filters.
Especially the third point was important for me. Although this is also possible with liquid by inserting every node into the wiki, I wanted a simpler solution. By selecting node types there is a quick way of selecting which part belongs to the wiki and which does not (and I mostly select all node types in wikitools).
The fourth point addresses the issue that, although your input filter supports the full mediawiki syntax, it only links to nodes inside the wiki (if all nodes are inside the wiki this is not really an issue). By using freelinking or pearwiki_filter, wikitools works together with a broader set of input filters.
The last point was the problem of your absence. The base development for wikitools was done beginning of February where it looked like liquid was abandoned.
Nevertheless I am sure we could team up to see about the future development of wiki concepts inside Drupal.
Thanks for your answer. And
Thanks for your answer. And let me start by saying that I'm terribly sorry about me not being able to respond to requests and update the Liquid module in a timely fashion during the past year.
Also, don't get me wrong. I'm not trying to create a conflict between our solutions and there might very well be a need for several wiki approaches in Drupal. However, if we are aiming at the same goal - and judging from your comments above, I think we are - there might be spin-off effects from working together to provide the community with a competent wiki solution.
I just down some comments on your points above, they are not very well phrased but I'm in a hurry:
Point three in your argument is interesting. I've had several thoughts about redesigning the core of the liquid name-binding solution to closer mimic the workings of Freelinking as well as to polish the current "bind wiki-id to node title" hack. I've also considered making the name-binding functionality "replacible" in the sense that the default module could be exchanged for another (for instance a proxy module for Freelinking). I'll get back to you about this as soon as I find a neat solution.
Most problems related to the fourth point will be addressed (and hopefully solved) with the new Liquid Filter module. My aim is to create a proxy module for the pearwiki filters and I hope that other developers will provide proxies or update the wiki-filter modules to support Liquid Filter.
With respect to point two. What options are you missing support for in Liquid? Both move protection and unique titles can (as far as I'm aware) be configured.
I'm aware that Liquid does not support all features that one could wish for in it's current state. However, the main goal of liquid isn't to create a fully featured wiki engien but rather to create a modular infrastructure for wiki functionality in Drupal. Needed wiki features should be (or will be) possible to achieve with Liquid by using addons.
Best regards,
Soren
I just try to provide as
I just try to provide as much as possible with as little dependencies as possible. So if I can provide a wiki-like functionality (e.g. automatic redirect) without the need of a 'wiki' module, I prefer it that way.
About your input filter framework: What will it provide which is not available with the normal Drupal framework? I know the Drupal framework is sometimes limiting since you don't have any context, but I found me not really hindered by it.
It would be interesting if you can give us an overview of your proposed structure for liquid - filter framework and also in general. That way we could better plan the future development of Drupal's wiki modules.
Just a quick question that's
Just a quick question that's not really relevant to the topic, but is the next release of Liquid going to be in the near future? Because rotzi's implementation seems to have a lot more functionality than Liquid as of now.
Back on topic, I do hope that you two can somehow come up with a way to work together. A functional wiki for Drupal would really bump it up a ton of points in comparison to other CMS's which already have this functionality.