<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Database Filesystem</title>
	<atom:link href="http://toosigma.com/archive/2005-08-05/database-filesystem/feed/" rel="self" type="application/rss+xml" />
	<link>http://toosigma.com/archive/2005-08-05/database-filesystem/</link>
	<description>far from normal</description>
	<pubDate>Wed, 08 Feb 2012 03:57:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: bjhorn</title>
		<link>http://toosigma.com/archive/2005-08-05/database-filesystem/comment-page-1/#comment-4</link>
		<dc:creator>bjhorn</dc:creator>
		<pubDate>Sun, 07 Aug 2005 22:43:10 +0000</pubDate>
		<guid isPermaLink="false">http://toosigma.com/archive/archive/2005-08-05/database-filesystem/#comment-4</guid>
		<description>I actually have a system that works somewhat like that, but it only works for certain types of files.  The system I use is based on the wiki technology, and is built into a simple program called Notebook, available at &lt;a href="http://www.wjduquette.com/notebook" rel="nofollow"&gt;http://www.wjduquette.com/notebook&lt;/a&gt;.  Unfortunately, it doesn't allow for things like images or complicated print formatting.  Since a number of the files I'm using for the campaign include such media files, it does prove less useful.

There's also the fact that putting together a mini-webpage would require a decent amount of coding and effort to appropriately arrange everything, it would almost take more effort and energy than simply suffering through the existing file systems.  Though I have to admit such a webpage would make for a really neat way to display everything.</description>
		<content:encoded><![CDATA[<p>I actually have a system that works somewhat like that, but it only works for certain types of files.  The system I use is based on the wiki technology, and is built into a simple program called Notebook, available at <a href="http://www.wjduquette.com/notebook" rel="nofollow">http://www.wjduquette.com/notebook</a>.  Unfortunately, it doesn&#8217;t allow for things like images or complicated print formatting.  Since a number of the files I&#8217;m using for the campaign include such media files, it does prove less useful.</p>
<p>There&#8217;s also the fact that putting together a mini-webpage would require a decent amount of coding and effort to appropriately arrange everything, it would almost take more effort and energy than simply suffering through the existing file systems.  Though I have to admit such a webpage would make for a really neat way to display everything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://toosigma.com/archive/2005-08-05/database-filesystem/comment-page-1/#comment-3</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Sat, 06 Aug 2005 03:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://toosigma.com/archive/archive/2005-08-05/database-filesystem/#comment-3</guid>
		<description>In the interim, you could put a tiny li'l web page together based completely on your laptop with categorized links and cross-references to where the files are located on the system. While this does not eliminate the need to file it in one specific place, it does allow one to make multiple references to the file without the OS impact of making shortcuts or links all over the place. This also has the added benefit of being able to rapidly organize things for specific sessions. There are a lot of ways to do it, but I think that this is the closest to the ideal and requires the least amount of upkeep.</description>
		<content:encoded><![CDATA[<p>In the interim, you could put a tiny li&#8217;l web page together based completely on your laptop with categorized links and cross-references to where the files are located on the system. While this does not eliminate the need to file it in one specific place, it does allow one to make multiple references to the file without the OS impact of making shortcuts or links all over the place. This also has the added benefit of being able to rapidly organize things for specific sessions. There are a lot of ways to do it, but I think that this is the closest to the ideal and requires the least amount of upkeep.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

