<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://mfgames.com/lib/exe/css.php?s=feed" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Moonfire Games</title>
    <subtitle></subtitle>
    <link rel="alternate" type="text/html" href="http://mfgames.com/"/>
    <id>http://mfgames.com/</id>
    <updated>2010-05-02T13:34:37-07:00</updated>
    <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
<link rel="self" type="application/atom+xml" href="http://mfgames.com/feed.php" />
    <entry>
        <title>Moonfire Games - Adding the language code to the toolchain name.</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/start?rev=1272831544&amp;do=diff"/>
        <published>2010-05-02T13:19:04-07:00</published>
        <updated>2010-05-02T13:19:04-07:00</updated>
        <id>http://mfgames.com/start?rev=1272831544&amp;do=diff</id>
        <author>
            <name>D. Moonfire</name>
        </author>
        <summary>Welcome to the Moonfire Games website. This site is a collection of various software and games, both computer and paper. Mostly the work of one person, Dylan R. E. Moonfire, it also includes contributes from many others.

There is no one focus of this site. It bobs around as interests rise and drop. One good way of getting something developed is to ask questions, to start to use it, or just express an interest. That is how many of the things here are developed, because someone wants it.</summary>
    </entry>
    <entry>
        <title>Standards</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/standards/start?rev=1272828554&amp;do=diff"/>
        <published>2010-05-02T12:29:14-07:00</published>
        <updated>2010-05-02T12:29:14-07:00</updated>
        <id>http://mfgames.com/standards/start?rev=1272828554&amp;do=diff</id>
        <author>
            <name>D. Moonfire</name>
        </author>
        <summary>There is a certain style with code on this project. Much if it comes from history and ascetics, but implementing those standards makes it easier to maintain and integrate code with the main line. The formatting rules on this page are the general rules, there may be language-specific elements below.</summary>
    </entry>
    <entry>
        <title>Zen and the Art of Coding Standards</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/presentations/zen-coding-standards?rev=1272827381&amp;do=diff"/>
        <published>2010-05-02T12:09:41-07:00</published>
        <updated>2010-05-02T12:09:41-07:00</updated>
        <id>http://mfgames.com/presentations/zen-coding-standards?rev=1272827381&amp;do=diff</id>
        <author>
            <name>D. Moonfire</name>
        </author>
        <summary>Standards are an important part of any project. For personal projects, like many of the ones on this site, the standards are internalized by the developers. They may have a short document describing the standards or it may be an epic that no one uses because it simply can’t be memorized by anyone.</summary>
    </entry>
    <entry>
        <title>Versions - created</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/versions?rev=1246014319&amp;do=diff"/>
        <published>2009-06-26T04:05:19-07:00</published>
        <updated>2009-06-26T04:05:19-07:00</updated>
        <id>http://mfgames.com/versions?rev=1246014319&amp;do=diff</id>
        <summary>For all the projects on this site, unless otherwise noted, we use a consistent versioning scheme to describe the releases. This version number gives an indication of the stability of a given package, but also to determine ABI and API compatibility.</summary>
    </entry>
    <entry>
        <title>Documentation</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/mfgames-cil/documentation/start?rev=1245517723&amp;do=diff"/>
        <published>2009-06-20T10:08:43-07:00</published>
        <updated>2009-06-20T10:08:43-07:00</updated>
        <id>http://mfgames.com/mfgames-cil/documentation/start?rev=1245517723&amp;do=diff</id>
        <author>
            <name>D. Moonfire</name>
        </author>
        <summary>MfGames CIL is a collection of utility classes and functions that are useful when coding in C# and other CIL (Common Infrastructure Language or a fancy way of saying VB.NET, Boo, C#, F#, etc). Some of these classes don’t really fit into a more specialized assembly while others function as the base of the other MfGames libraries and tools.</summary>
    </entry>
    <entry>
        <title>Conversion</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/mfgames-cil/documentation/conversion?rev=1245517662&amp;do=diff"/>
        <published>2009-06-20T10:07:42-07:00</published>
        <updated>2009-06-20T10:07:42-07:00</updated>
        <id>http://mfgames.com/mfgames-cil/documentation/conversion?rev=1245517662&amp;do=diff</id>
        <author>
            <name>D. Moonfire</name>
        </author>
        <summary>This library provides a series of conversion routines. At their base level, they function like System.Convert, but also enable a pluggable conversion routines that goes beyond implementing IConvertible.

The top-level functionality, ExtendedConvert requires the utility namespace:</summary>
    </entry>
    <entry>
        <title>Annotations - created</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/mfgames-cil/documentation/annotations?rev=1245379258&amp;do=diff"/>
        <published>2009-06-18T19:40:58-07:00</published>
        <updated>2009-06-18T19:40:58-07:00</updated>
        <id>http://mfgames.com/mfgames-cil/documentation/annotations?rev=1245379258&amp;do=diff</id>
        <author>
            <name>D. Moonfire</name>
        </author>
        <summary>The MfGames.Utility.Annotations namespace is a container namespace for various code annotations. We use ReSharper as our primary tool of choice. There are many tools that help development.

Thankfully, the folks at JetBrains let us use a copy of their annotation attributes to help ReSharper make more intelligent decisions.</summary>
    </entry>
    <entry>
        <title>Documentation</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/unit-timing-cil/documentation/start?rev=1244338091&amp;do=diff"/>
        <published>2009-06-06T18:28:11-07:00</published>
        <updated>2009-06-06T18:28:11-07:00</updated>
        <id>http://mfgames.com/unit-timing-cil/documentation/start?rev=1244338091&amp;do=diff</id>
        <summary>*  Getting Started: A brief introduction to Unit Timing including the minimum to get it up and running.
*  Attributes:
	*  [Timing]: Indicates a method which needs to be run repeatedly and timed.
	*  [TimingBaseline]: Indicates a method used to calculate the overhead of the timing methods.</summary>
    </entry>
    <entry>
        <title>[Timing] Attribute</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/unit-timing-cil/documentation/timing-attribute?rev=1244338015&amp;do=diff"/>
        <published>2009-06-06T18:26:55-07:00</published>
        <updated>2009-06-06T18:26:55-07:00</updated>
        <id>http://mfgames.com/unit-timing-cil/documentation/timing-attribute?rev=1244338015&amp;do=diff</id>
        <summary>The [Timing] attribute indicates a method that is to be run a number of times while measuring the total length of time it takes to complete.

There can be more than one [Timing] method in a class.

Iterations

An iteration is simply a number of times to run a method as part of a single time measurement. The simplest form of this attribute is just a single number which produces a single measurement.</summary>
    </entry>
    <entry>
        <title>[TimingBaseline] Attribute - created</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/unit-timing-cil/documentation/timing-baseline-attribute?rev=1244337966&amp;do=diff"/>
        <published>2009-06-06T18:26:06-07:00</published>
        <updated>2009-06-06T18:26:06-07:00</updated>
        <id>http://mfgames.com/unit-timing-cil/documentation/timing-baseline-attribute?rev=1244337966&amp;do=diff</id>
        <summary>A baseline measures the amount of time it takes to perform actions integral to performing the actual measurements. The basic baseline measures the time it takes to repeatedly call a method. This is done in the same way as methods marked with the [Timing] Attribute are called.</summary>
    </entry>
    <entry>
        <title>Unit Timing CIL - Links to unit-timing-cil:documentation changed to unit-timing-cil:documentation:start</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/unit-timing-cil/start?rev=1244336853&amp;do=diff"/>
        <published>2009-06-06T18:07:33-07:00</published>
        <updated>2009-06-06T18:07:33-07:00</updated>
        <id>http://mfgames.com/unit-timing-cil/start?rev=1244336853&amp;do=diff</id>
        <summary>*  Audience: Developers
*  Created: 2009-04-28
*  License: MIT
*  Language: CIL, C#


A CIL (.NET) library and tools written for performing timing tests on small blocks of code. Each block of code may be run many times to show performance in a series or to perform enough to collect meaningful data. This project provides a framework for annotating source code with attributes, tools for collecting and reporting on results, and a library for integration with third-party components.</summary>
    </entry>
    <entry>
        <title>Getting Started - Page moved from unit-timing-cil:getting-started to unit-timing-cil:documentation:getting-started</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/unit-timing-cil/documentation/getting-started?rev=1244336822&amp;do=diff"/>
        <published>2009-06-06T18:07:02-07:00</published>
        <updated>2009-06-06T18:07:02-07:00</updated>
        <id>http://mfgames.com/unit-timing-cil/documentation/getting-started?rev=1244336822&amp;do=diff</id>
        <summary>Unit Timing is intended to be a low-profile library that uses attribute annotation to identify small units of block of code to run repeatedly and report the results. All of the attributes are located in the top namespace, so the following using line is required:</summary>
    </entry>
    <entry>
        <title>Scratch an Itch - created</title>
        <link rel="alternate" type="text/html" href="http://mfgames.com/scratch-an-itch?rev=1241577569&amp;do=diff"/>
        <published>2009-05-05T19:39:29-07:00</published>
        <updated>2009-05-05T19:39:29-07:00</updated>
        <id>http://mfgames.com/scratch-an-itch?rev=1241577569&amp;do=diff</id>
        <summary>One of the philosophies of this site, and the work done on it, is “scratching an itch.” Open source projects, no matter if it is writing, programming, or gaming, come up when someone sees something they need and decides to do something about it. Many of the libraries on this site are such an itch. Once they are written, they are maintained as appropriate, but the fulfill our needs. Others might be interested in additional functional, so we are welcome to any suggestions, feedback, or even additi…</summary>
    </entry>
</feed>
