It is possible on wiki, and needs only a rather simple change of the wikiengine to supply the prerequisites for it to develop.
Multilingual communication will not neccessarily happen when wikiengines are improved, but it surely will not happen if they are not changed.
As this is a wikilandia-wide issue and concerns different wikiengines and various communities there is a "central" page on the "project" to keep informed about the allover developement.
Wikiserver(Site not responding. Last check: 2007-11-01)
A WikiServer is a WikiEngine* that is completely self-contained - it includes its own HTTP server, and so does not require CGI support, Perl, or even a separate Web server such as Apache or IIS.
As such, it is one of the easiest ways to install and run a wiki; even people without any knowledge about the system can set up a wikiserver without many problems.
It is usually implemented as a server-side script that runs on one or more web servers, with the content generally stored in a relational database management system, although some implementations use the server's file system instead.
Similarly, it is hard for a new feature or a new WikiEngine to be adopted by many wiki communities; wiki communities are “stuck” with their current wiki engine, because it is hard to move the content to a new one.
But ideas like making it easy for individuals and wiki communities to change WikiEngines, and making it easier to merge different wikiforks seem to be different from that (although related in that the ultimate goal of both is to speed up wiki software evolution).
Maybe the reason the original WikiEngine has not forked in the common understanding of the term but more “exploded”, is because we’re still exploring ways of understanding an addition that is not another step on the evolutionary expansion of a paradigm (e.g.
The historical and some might claim canonical term is actually "WikiClone", a term originally coined to describe sites built with software imitating the WikiWiki idea before WikiEngines were common.
FridemarPache has since rebuilt the entire ontology at WikiWiki to be more consistent and clear; i.e.
I'd be interested in knowing how many lines of code the various WikiEngines are, if anyone has any of these figures handy (I am of the mind that the less lines of code, the better) -- BayleShanks
Category talk:Lizzy - WikiIndex(Site not responding. Last check: 2007-11-01)
I am still grasping with this concept and I think you are saying something that might be a resolution for us.
If we use a WikiEngine template that gets rid of some offending code, I would love the WikiEnginewiki to be in the category:wikiengine space.
However, if that is not easy, not reasonable or doesn't work, we should put the pointer to the wiki on a non-category page, until we figure out a solution.
wikiindex.com /Category_talk:Lizzy (357 words)
[Jspwiki-users] 2.3.21 and still Anonymous(Site not responding. Last check: 2007-11-01)
Looking at it, I'm wondering if all methods that create or make a request for a URL should be moved into WikiContext to assure that parameters are always preserved.
This should not be too much of a hardship as contexts are used almost everywhere already (and in many cases just as a means to get at a WikiEngine).
Possibly it might make sense to reduce the visibility of both WikiContext constructors to *package* level to assure that WikiEngine.createContext() is the always used (it seems to do some important looking voodoo).
Subversion seems to be more suitable than CVS for our coding needs, and Trac is very good both as a repository front-end and a bug-tracking (trouble-ticket) system.
It’s just that Trac’sWikiEngine should either resemble or better yet use DokuWiki’s Engine.
The problem with this integration, IMHO, is using CVS and MoinMoin, which I’d prefer instead to be replaced by Subversion and DokuWiki.
First, it has very little to do with the WikiEngine.
I have a question about the last list update: World66Wiki, located on position 3, seems to be not a wiki rather than a application development framework known as Zope.
I have not found a source describing that ZWiki, the WikiEngine based on Zope, was used to build Word66.
[Pmwiki-users] adding PmWiki/WikiEngine and question about upgrading(Site not responding. Last check: 2007-11-01)
With the holiday season and my move to a new apartment I'm just now catching up on some email messages...
On Tue, Dec 16, 2003 at 05:14:21PM +0100, Christian Ridderstr?m wrote: > I needed a page that just quickly describes what a WikiEngine is, and > since this page logically should be in the group PmWiki, I created it here: > http://www.pmichaud.com/wiki/PmWiki/WikiEngine > I hope this is the correct way to behave, i.e.
If not please let me know how I should go about when adding > documentation to PmWiki.
23.02.2005 11:29:44 org.apache.catalina.core.ApplicationContext log INFO: Assigning new log to 25899876 23.02.2005 11:29:44 org.apache.catalina.core.ApplicationContext log INFO: No jspwiki.propertyfile defined for this context, using default from /WEB-INF/jspwiki.properties 23.02.2005 11:29:56 org.apache.catalina.core.ApplicationContext log INFO: Application 25899876 requests WikiEngine.
- [http://moinmoin.wikiwikiweb.de/ (website)] - discussion of the WikiEngineMoinMoinWiki
- [http://twiki.org/cgi-bin/view/Main/WebHome (website)] - a "web" of pages for discussion of the WikiEngineTWiki
wiki - [http://www.usemod.com/cgi-bin/wiki.pl (website)] - first wiki running the Perl-based and AtisWiki-derived UseModWikiWikiEngine by Clifford Adams
