<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Radical Blue Gaming &#187; development process</title>
	<atom:link href="https://www.radblue.com/tag/development-process/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.radblue.com</link>
	<description></description>
	<lastBuildDate>Mon, 30 Mar 2026 20:17:15 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.8.31</generator>
	<item>
		<title>A look at the RGS Tester Toolkit &#8211; the Start-up Algorithm</title>
		<link>https://www.radblue.com/2013/05/rgs-ttk-startupalgorithm/</link>
		<comments>https://www.radblue.com/2013/05/rgs-ttk-startupalgorithm/#comments</comments>
		<pubDate>Mon, 06 May 2013 16:10:10 +0000</pubDate>
		<dc:creator><![CDATA[sam]]></dc:creator>
				<category><![CDATA[blog]]></category>
		<category><![CDATA[development process]]></category>
		<category><![CDATA[egm testing]]></category>
		<category><![CDATA[g2s]]></category>
		<category><![CDATA[game to system]]></category>
		<category><![CDATA[products]]></category>
		<category><![CDATA[rgs]]></category>
		<category><![CDATA[startup algorithm]]></category>
		<category><![CDATA[tester toolkit]]></category>

		<guid isPermaLink="false">http://www.radblue.com/?p=4199</guid>
		<description><![CDATA[The Tester Toolkit is an optional module for RGS that lets you customize and extend RGS testing functionality. The Tester Toolkit consists of three main features &#8211; the Start-up Algorithm, Custom Scripting and the Response Manager. Each of these features allow you to extend your ability to test G2S EGMs. In this post, we explore [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The <a href="https://www.radblue.com/products/rgs/"><span style="font-size: large;">Tester Toolkit</span></a> is an optional module for RGS that lets you customize and extend RGS testing functionality. The Tester Toolkit consists of three main features &#8211; the Start-up Algorithm, Custom Scripting and the Response Manager. Each of these features allow you to extend your ability to test G2S EGMs. In this post, we explore the advantages of the Start-up Algorithm, who uses it and why.</p>
<hr />
<p>The start-up algorithm is the list of commands that get sent when RGS receives a <code>commsOnline</code> command from an EGM to initiate G2S communications. The list of commands is automatically filtered by the devices present in the EGM’s <code>descriptorList</code>. In the standard RGS, you can include or exclude G2S commands in the fixed start-up algorithm list, which is useful if your EGM doesn&#8217;t support one or more of the commands in the list, but you cannot reorder any of the commands or change any settings within any of the commands.</p>
<p>In the Tester Toolkit, the Start-up Algorithm editor is enhanced to provide you with complete control over the order of commands and their contents, to customize the algorithm as needed to simulate any host.You can also save a copy of the modified algorithm, making it easy to switch between different versions to meet various test environments.</p>
<p>Why would you need that much flexibility, you ask? Let&#8217;s take a look.</p>
<p><a href="https://www.radblue.com/wp-content/uploads/2013/05/rgs_ttk_whyStartupAlgorithm.png"><img class="alignleft size-large wp-image-4389" alt="The advantages of a custom startup algorithm" src="https://www.radblue.com/wp-content/uploads/2013/05/rgs_ttk_whyStartupAlgorithm-1024x778.png" width="598" height="454" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Whether you are an EGM developer coding against a particular host, a tester trying to improve integration with a specific vendor or trying to troubleshoot an issue in the field, being able to recreate the start-up algorithm accurately can save countless hours in tracking down issues. In any case, the process efficiencies and product improvements spell big savings.</p>
<p>If you are pre-testing EGMs before moving them to the slot floor, not only can you find issues before they happen in a live environment, you&#8217;ll have the information you need to better communicate issues back to the vendor. This means faster issue resolution and easier installs.</p>
<p>Creating custom algorithms in RGS is <em>easy</em> with a simple drag-and-drop interface.</p>
<p><a href="https://www.radblue.com/wp-content/uploads/2013/05/editStartupAlgorithm.png"><img class="alignleft size-full wp-image-4256" alt="" src="https://www.radblue.com/wp-content/uploads/2013/05/editStartupAlgorithm.png" width="478" height="327" /></a>Once you&#8217;ve created a custom algorithm, just make it the active RGS start-up algorithm and start communications with the EGM. You can choose to run the algorithm to the end or to step through the algorithm, which lets you choose when to send each command or to skip commands altogether.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>For more information on the Tester Toolkit, head over to the <a href="https://www.radblue.com/products/rgs/">RGS product page</a>. If you&#8217;d like to try it out, <a href="mailto:sales@radblue.com">just let us know</a>.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>https://www.radblue.com/2013/05/rgs-ttk-startupalgorithm/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A new relationship</title>
		<link>https://www.radblue.com/2010/08/a-new-relationship/</link>
		<comments>https://www.radblue.com/2010/08/a-new-relationship/#comments</comments>
		<pubDate>Tue, 24 Aug 2010 21:29:37 +0000</pubDate>
		<dc:creator><![CDATA[marty]]></dc:creator>
				<category><![CDATA[blog]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[development process]]></category>
		<category><![CDATA[smartphone]]></category>
		<category><![CDATA[software development trends]]></category>

		<guid isPermaLink="false">http://www.radblue.com/?p=1156</guid>
		<description><![CDATA[One of the keys to the success of the Android phones (and the iPhones as well) is the application marketplace. Whether you really need access to 80,000 apps on your smartphone is an separate topic. What is more interesting is what attributes are common among the most popular apps. The #1 thing I see is [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>One of the keys to the success of the Android phones (and the iPhones as well) is the application marketplace. Whether you really <em>need</em> access to 80,000 apps on your smartphone is an separate topic. What is more interesting is what attributes are common among the most popular apps.</p>
<p>The #1 thing I see is the feedback loop. The most successful apps, the ones that are downloaded the most, constantly have reviews that say &#8220;the developer listened to me and got back to me.&#8221; Even for the apps that have growing pains (adapting to new hardware, adapting to OS updates or adding new features) the customers are forgiving if they feel part of the process, part of the loop. Otherwise excellent apps are downgraded if the developer, for whatever reason, chooses not to respond to customers.</p>
<p>I am a prime example. I have worked with a small development shop with an app that worked on my original Droid, but died on my Droid X. I am pretty sure the developers couldn&#8217;t afford to get a Droid X, so they used me as their test lab. They were very responsive, very involved and I never felt abandoned. This feedback loop kept me from dumping their app and looking for an alternative.</p>
<p>The #2 thing that I see in the most successful apps is a continuous stream of releases. Bug fixes, corrections for different hardware, new features, even small tweaks are part of a steady stream of updates. And the best developers go out of their way to acknowledge that the changes are driven by their customers.</p>
<p>There are a number of other interesting attributes of successful apps that I could add, but these are the main factors that strike me as revolutionary in terms of software developed for the consumer market.</p>
<p>Whether by choice or by the desires of the market, the Android marketplace has adopted many of the practices found in the Agile movement. I would venture that with the proliferation of these devices, the way customers interact with, and the expectations they have from, software developers in markets of all sizes and shapes are going to fundamentally change. A new relationship is being forged between the customer and the developer. I think this new relationship will be a primary factor in deciding who wins and who loses going forward.</p>
<p>Here at RadBlue, we live Agile, breath, Agile and see its benefits daily.</p>
<p>Welcome to the new world.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.radblue.com/2010/08/a-new-relationship/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
