<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/crownandcutlass/feature-requests/</id><updated>2008-01-28T19:47:35Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Implement GameState Test</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/16/" rel="alternate"/><published>2008-01-28T19:47:35Z</published><updated>2008-01-28T19:47:35Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.nete037f0bf1f2b825c0f35e65e36d13f036c0cb5b3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Crown and Cutlass needs a gamestate test framework so that we can test individual gamestates without having to run the entire game.  It should be similar to our Protocce test framework, except only a single game state test should be specified on the command-line.  Something like this maybe:&lt;/p&gt;
&lt;p&gt;class IGameStateTest {&lt;br /&gt;
public:&lt;br /&gt;
// Method to do generic unit tests on this gamestate&lt;br /&gt;
virtual void vTest() {};&lt;br /&gt;
virtual void vInitialize() = 0;&lt;br /&gt;
virtual void vShutdown() {};&lt;/p&gt;
&lt;p&gt;IGameStatePtr GameState() { return mState; };&lt;/p&gt;
&lt;p&gt;private:&lt;br /&gt;
IGameStatePtr mState;&lt;br /&gt;
}&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Investigate GUI systems</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/15/" rel="alternate"/><published>2008-01-28T19:42:23Z</published><updated>2008-01-28T19:42:23Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.net989733a78e0a0cea84c08b04e76599f9e88adc57</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;We have been planning to use CEGUI for the GUI, but Navi sounds interesting:&lt;br /&gt;
&lt;a href="http://navi.agelessanime.com/wiki/index.php/Main_Page" rel="nofollow"&gt;http://navi.agelessanime.com/wiki/index.php/Main_Page&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Implement scripting</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/14/" rel="alternate"/><published>2008-01-28T19:39:37Z</published><updated>2008-01-28T19:39:37Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.net04a9937f547402876dfc1effdc5031d67dba75f8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;We would like to expose the public Protocce interface to a scripting environment.  Possibly Squirrel (http://squirrel-lang.org/default.aspx) or Javascript (especially if we go with an HTML-based GUI system).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Flush out FindVorbis.cmake</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/13/" rel="alternate"/><published>2007-02-27T20:44:51Z</published><updated>2007-02-27T20:44:51Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.net8cd9033f6348241fbd94ca9240fb8db31fc1c18b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I wrote a really bare-bones FindVorbis.cmake:&lt;br /&gt;
&lt;a href="http://crownandcutlass.svn.sourceforge.net/viewvc/crownandcutlass/trunk/Protocce/cmake/FindVorbis.cmake?revision=744&amp;amp;view=markup"&gt;http://crownandcutlass.svn.sourceforge.net/viewvc/crownandcutlass/trunk/Protocce/cmake/FindVorbis.cmake?revision=744&amp;amp;view=markup&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Flush that out, or replace it with a more official version.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Implement a sound test</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/12/" rel="alternate"/><published>2007-02-23T18:56:31Z</published><updated>2007-02-23T18:56:31Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.netdf431dc96c76cb752e7d33f39672ace27509e621</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;We need to test our sound code.  I have added "interactive" test functionality to our test framework so that we can have the user verify that the audio file played correctly.  Implement an "interactive" sound test.  Test initialization, load an ogg sample and play it, load a wave sample and play it, and then test shutdown.  After playing each sample, confirm that the user heard what was expected.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add iteration support to PropertyBag</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/11/" rel="alternate"/><published>2007-02-22T23:23:47Z</published><updated>2007-02-22T23:23:47Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.net2042889d07eb3fab02d6769d1d430d9a3b0c7cd5</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Our property bag class (you can see the header here &lt;a href="http://crownandcutlass.svn.sourceforge.net/viewvc/crownandcutlass/trunk/Protocce/include/PropertyBag.h?revision=739&amp;amp;view=markup"&gt;http://crownandcutlass.svn.sourceforge.net/viewvc/crownandcutlass/trunk/Protocce/include/PropertyBag.h?revision=739&amp;amp;view=markup&lt;/a&gt; ) currently does not support iteration over the properties.  Add that functionality.&lt;/p&gt;
&lt;p&gt;Unfortunately, I do not currently know anything about writing custom iterators.  One quick and simple solution would be to add a method ("GetProperties()" or something) that returns a list of tPropertyMapPair.  tPropertyMapPair should probably be renamed tPropertyBagPair if it is going to be used outside of the PropertyBag implementation.&lt;/p&gt;
&lt;p&gt;Explain your solution and why it is preferable over the alternatives.  Since this is an area I am unfamiliar with, I would like to learn why you took the approach you did.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>CMake Review</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/10/" rel="alternate"/><published>2007-02-22T23:09:28Z</published><updated>2007-02-22T23:09:28Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.net5e76c2565f8f4e6ec9437a100fad0d31d75ecb10</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;We are very new to using CMake.  While we have gotten builds working quickly and easily, we would appreciate a review by someone with more CMake experience.  Let us know if you take a look at the CMake files and if you find anything that could be improved.&lt;/p&gt;
&lt;p&gt;This item may be open for a while, as multiple reviews would be ideal.&lt;/p&gt;
&lt;p&gt;This tracker item is related:&lt;br /&gt;
&lt;a href="http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1660920&amp;amp;group_id=110607&amp;amp;atid=656857"&gt;http://sourceforge.net/tracker/index.php?func=detail&amp;amp;aid=1660920&amp;amp;group_id=110607&amp;amp;atid=656857&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>C++ Review</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/9/" rel="alternate"/><published>2007-02-22T23:06:09Z</published><updated>2007-02-22T23:06:09Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.netb71812b21d239f7adb366a41d9194df203cfbe20</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;We are somewhat competent in C++, but we are still learning how to use C++ safely and effectively.  Review our code for errors.  While there may be a whole set of issues I am unaware of, pay particular attention to:&lt;br /&gt;
- const correctness&lt;br /&gt;
- Pass-by value/pointer/reference correctness&lt;br /&gt;
- Missing, unnecessary, or incorrect copy-constructors and assignment operators&lt;br /&gt;
- Memory issues (leaks, null pointer dereferences, reference-counted pointer cycles, etc.)&lt;/p&gt;
&lt;p&gt;Because we are in the middle of the rewrite, I expect this will be something that we leave open for a while and hopefully get multiple reviews.&lt;/p&gt;
&lt;p&gt;Note: While it would be helpful to note inconsistencies in our style, this is not a good place for discussion about the merits of the style we use.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Implement serialization system</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/8/" rel="alternate"/><published>2007-02-15T21:09:09Z</published><updated>2007-02-15T21:09:09Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.net8a77e589a6a944bd75ac3b4b20419e61b4950083</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Implement serialization system.  It should allow at least XML serialization for now, with the ability to support other formats if necessary later.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Implement Sound System</title><link href="https://sourceforge.net/p/crownandcutlass/feature-requests/7/" rel="alternate"/><published>2007-02-15T21:07:05Z</published><updated>2007-02-15T21:07:05Z</updated><author><name>David Thulson</name><uri>https://sourceforge.net/u/dthulson/</uri></author><id>https://sourceforge.net8a494feed4bdc25a3e40a4fa3e2a0f1a1c95842d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Implement the sound system using sound resources as a test/demo of the resource management system.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>