<?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: Projects&#8230;</title>
	<atom:link href="http://toosigma.com/archive/2006-05-12/projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://toosigma.com/archive/2006-05-12/projects/</link>
	<description>far from normal</description>
	<pubDate>Wed, 08 Feb 2012 02:52:07 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: BJ</title>
		<link>http://toosigma.com/archive/2006-05-12/projects/comment-page-1/#comment-349</link>
		<dc:creator>BJ</dc:creator>
		<pubDate>Mon, 15 May 2006 18:06:56 +0000</pubDate>
		<guid isPermaLink="false">http://toosigma.com/archive/archive/2006-05-12/projects/#comment-349</guid>
		<description>Unfortunately, that level of interactivity is slightly beyond my current toolset.  If I really want to get into that sort of thing, I should work on a Java-based client-server system.  The Javascript solution would be networkless, thus I'd have to give you AC/Alignment/Type, and have the calculator handle the details from there.

I won't deny that a full-blown encounter manager that would handle all the details you've mentioned hasn't crossed my mind more than once in the past year or two.  However, it is probably a bit out of reach as far as my own time investment is concerned.  Maybe if I brush up on my Java, and find some easy-to-use libraries to handle the background stuff (user interface, networking, communication), I'll get around to building something along those lines.</description>
		<content:encoded><![CDATA[<p>Unfortunately, that level of interactivity is slightly beyond my current toolset.  If I really want to get into that sort of thing, I should work on a Java-based client-server system.  The Javascript solution would be networkless, thus I&#8217;d have to give you AC/Alignment/Type, and have the calculator handle the details from there.</p>
<p>I won&#8217;t deny that a full-blown encounter manager that would handle all the details you&#8217;ve mentioned hasn&#8217;t crossed my mind more than once in the past year or two.  However, it is probably a bit out of reach as far as my own time investment is concerned.  Maybe if I brush up on my Java, and find some easy-to-use libraries to handle the background stuff (user interface, networking, communication), I&#8217;ll get around to building something along those lines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip</title>
		<link>http://toosigma.com/archive/2006-05-12/projects/comment-page-1/#comment-338</link>
		<dc:creator>Philip</dc:creator>
		<pubDate>Fri, 12 May 2006 22:34:28 +0000</pubDate>
		<guid isPermaLink="false">http://toosigma.com/archive/archive/2006-05-12/projects/#comment-338</guid>
		<description>Mmm...combat calculators...Gonna set it up so your GMness puts in ACs, alignments, types, and such, which we don't see, and then we select our combat options that apply and click "FIRE!"? Also, you could configure something on your side that lets you preload some things that will be revealed to individuals and simply select and send them to individuals at the appropriate time. Mayhap a more elaborate encounter manager which includes the combat calculator?</description>
		<content:encoded><![CDATA[<p>Mmm&#8230;combat calculators&#8230;Gonna set it up so your GMness puts in ACs, alignments, types, and such, which we don&#8217;t see, and then we select our combat options that apply and click &#8220;FIRE!&#8221;? Also, you could configure something on your side that lets you preload some things that will be revealed to individuals and simply select and send them to individuals at the appropriate time. Mayhap a more elaborate encounter manager which includes the combat calculator?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

