<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Wiki Refresher</title>
	<atom:link href="http://barelyenough.org/blog/2005/11/wiki-refresher/feed/" rel="self" type="application/rss+xml" />
	<link>http://barelyenough.org/blog/2005/11/wiki-refresher/</link>
	<description></description>
	<pubDate>Wed, 07 Jan 2009 01:31:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Devon Jones</title>
		<link>http://barelyenough.org/blog/2005/11/wiki-refresher/#comment-500</link>
		<dc:creator>Devon Jones</dc:creator>
		<pubDate>Mon, 28 Nov 2005 20:39:29 +0000</pubDate>
		<guid isPermaLink="false">http://pezra.barelyenough.org/blog/?p=184#comment-500</guid>
		<description>&lt;p&gt;So I've been screwing around with a one page application called TiddlyWiki.  In the course of messing with it, some of the people in the community have looked at creating a server integration so that multiple people can use tw, and have it store stuff on the server.  This is creating an interesting tool in that we may be able to have a documentation system that caches all of the wiki entries in an html file sitting on your system (so you have acccess to it offline) but will also update itself to the latest server wiki entries the next time you are on a network.  The experiences of working for Integware have really helped with the code I am writing for this, as essentially it appears possible to turn tiddlywiki into the front end of an entire document control system.&lt;/p&gt;

&lt;p&gt;Oh, and adding new syntax is a snap, as well as adding plugins.&lt;/p&gt;

&lt;p&gt;http://www.tiddlywiki.com/&lt;/p&gt;

&lt;p&gt;Devon&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>So I&#8217;ve been screwing around with a one page application called TiddlyWiki.  In the course of messing with it, some of the people in the community have looked at creating a server integration so that multiple people can use tw, and have it store stuff on the server.  This is creating an interesting tool in that we may be able to have a documentation system that caches all of the wiki entries in an html file sitting on your system (so you have acccess to it offline) but will also update itself to the latest server wiki entries the next time you are on a network.  The experiences of working for Integware have really helped with the code I am writing for this, as essentially it appears possible to turn tiddlywiki into the front end of an entire document control system.</p>
<p>Oh, and adding new syntax is a snap, as well as adding plugins.</p>
<p><a href="http://www.tiddlywiki.com/" rel="nofollow">http://www.tiddlywiki.com/</a></p>
<p>Devon</p>
]]></content:encoded>
	</item>
</channel>
</rss>
