<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Data-Driven Design</title>
	<link>http://programmerjoe.com/2007/02/21/data-driven-design/</link>
	<description>Whats with all the screaming?</description>
	<pubDate>Fri, 05 Sep 2008 18:45:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Joe</title>
		<link>http://programmerjoe.com/2007/02/21/data-driven-design/#comment-697</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Mon, 05 Mar 2007 18:05:46 +0000</pubDate>
		<guid>http://programmerjoe.com/2007/02/21/data-driven-design/#comment-697</guid>
		<description>That's fairly similar to what we're doing now.  We have a text file that defines the enum values and then access them by name (read: string) in the code.  We don't actually look them up in the code very often (or at all in some cases) so there isn't much of an efficiency hit there.  And the boost we get from designers being able to add their own enum values is huge.

If only we didn't have all those legacy enums... :)</description>
		<content:encoded><![CDATA[<p>That&#8217;s fairly similar to what we&#8217;re doing now.  We have a text file that defines the enum values and then access them by name (read: string) in the code.  We don&#8217;t actually look them up in the code very often (or at all in some cases) so there isn&#8217;t much of an efficiency hit there.  And the boost we get from designers being able to add their own enum values is huge.</p>
<p>If only we didn&#8217;t have all those legacy enums&#8230; <img src='http://programmerjoe.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Bryant</title>
		<link>http://programmerjoe.com/2007/02/21/data-driven-design/#comment-684</link>
		<dc:creator>Rich Bryant</dc:creator>
		<pubDate>Mon, 05 Mar 2007 10:25:54 +0000</pubDate>
		<guid>http://programmerjoe.com/2007/02/21/data-driven-design/#comment-684</guid>
		<description>There's a couple of ways but what seems to popular right now is to define a class which exposes a collection and load that collection from XML.

It's a workaround way to get some of the benefits of .NET's XML integration without using the framework.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a couple of ways but what seems to popular right now is to define a class which exposes a collection and load that collection from XML.</p>
<p>It&#8217;s a workaround way to get some of the benefits of .NET&#8217;s XML integration without using the framework.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://programmerjoe.com/2007/02/21/data-driven-design/#comment-673</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Mon, 05 Mar 2007 02:37:25 +0000</pubDate>
		<guid>http://programmerjoe.com/2007/02/21/data-driven-design/#comment-673</guid>
		<description>The only reason we're using compile-time enums is that they pre-date our use of XML by a couple years.  We really only started using XML extensively for static game data about 2.5 years ago, and some of these enums go back to the early days of the project over 4 years ago.  

It sounds like you're referring to a specific technique, though. Is there some sort of standard way to define enums in XML and then use them from C++ code?</description>
		<content:encoded><![CDATA[<p>The only reason we&#8217;re using compile-time enums is that they pre-date our use of XML by a couple years.  We really only started using XML extensively for static game data about 2.5 years ago, and some of these enums go back to the early days of the project over 4 years ago.  </p>
<p>It sounds like you&#8217;re referring to a specific technique, though. Is there some sort of standard way to define enums in XML and then use them from C++ code?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Bryant</title>
		<link>http://programmerjoe.com/2007/02/21/data-driven-design/#comment-670</link>
		<dc:creator>Rich Bryant</dc:creator>
		<pubDate>Mon, 05 Mar 2007 02:05:00 +0000</pubDate>
		<guid>http://programmerjoe.com/2007/02/21/data-driven-design/#comment-670</guid>
		<description>Hmm, hard coded enums?

Why not simply use strong typing instead and inherit from the XML?

Or is there an app-specific reason?</description>
		<content:encoded><![CDATA[<p>Hmm, hard coded enums?</p>
<p>Why not simply use strong typing instead and inherit from the XML?</p>
<p>Or is there an app-specific reason?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
