Wild thought: MartinCleaver is often saying what makes TWiki valuable is it's RenderingPipeline, could that pipeline be lifted straight into a client side application?

Indeed, I've been thinking about embedding that pipeline for a long time. I thought I'd been saying it as well, but I figure that I'd probably not done so explicitly. So here goes:

Please add your thoughts

Other applications where you would like to see TWiki's RenderingEngine:

Server side:

Client side:

Other thoughts:

• A proof of concept should be pretty easy to do: If clean RenderDotPm can be formed quickly by separating the rendering functions out of TWikiDotPm and PluginsDotPm, we would have created the basis for an embeddable TWiki Renderer, implantable in any number of applications written in Perl
  • The step after would be to expose those functions in a WebServices wrapper so that non-local and non-Perl applications could get as output the rendered HTML version of an input piece of WikiML.
• Its about time some standards body got together to form an XML-based PortableWikiInterchangeLanguage for swapping content between wikis and a CommonWikiShorthandNotation that Wikis could converge on.
• TWiki has perhaps the most comprehensive set of tags.
• Incompatibility locks people into platforms.
• We don't have enough people actively involved with TWiki development to implement these features.

-- MartinCleaver - 31 Dec 2002

Initial experimentation would be easy; just take a copy of the view script and modify it slightly. If successful common code could always be refactored at a later date.

-- JohnTalintyre - 31 Dec 2002

Has anyone tried putting Twiki into PostNuke using CrossNuke Modularizer? http://www.crossnuke.com/modules.php?op=modload&name=Plog&file=index&pop=Default&postCategoryId=26&blogId=2

-- IanAllinson - 23 Jan 2005