<?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"
	>
<channel>
	<title>Comments on: Thoughts on Strategy: Tracking Bugs</title>
	<atom:link href="http://flashforlearning.com/2006/10/thoughts-on-strategy-tracking-bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://flashforlearning.com/2006/10/thoughts-on-strategy-tracking-bugs/</link>
	<description>Knowledge Management &#62; Learning Strategy &#62; E-Learning &#62; Flash</description>
	<pubDate>Wed, 07 Jan 2009 02:48:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: &#8220;Flex&#8221;ing Development Muscles&#8230; &#8212; Flash For Learning</title>
		<link>http://flashforlearning.com/2006/10/thoughts-on-strategy-tracking-bugs/#comment-24004</link>
		<dc:creator>&#8220;Flex&#8221;ing Development Muscles&#8230; &#8212; Flash For Learning</dc:creator>
		<pubDate>Tue, 23 Oct 2007 15:24:06 +0000</pubDate>
		<guid isPermaLink="false">http://flashforlearning.com/2006/10/27/thoughts-on-strategy-tracking-bugs/#comment-24004</guid>
		<description>&lt;p&gt;[...] Remember a few months back when I wrote about QA? I got a QA entry linking to a database working right out of Articulate Presenter as a tool in the upper right-hand corner. Honestly, it&#8217;s just a link to a URL, so it could be linked to anything, but the point is I have it working out of Articulate, using the LMS to provide your name when you enter a bug and Articulate to auto-fill the slide number you&#8217;re on, so all you have to do is tag what the problem is with keywords and then write a detailed description of the problem, and submit. The last week or two, I&#8217;ve been working on the management system to handle all that QA data, and I&#8217;m using it as an excuse to learn Flex 2 and AMFPHP 2.0 (currently in 1.9 beta 2). It&#8217;s fast, it&#8217;s effective, it&#8217;s efficient, it&#8217;s clean and neat &#8212; I&#8217;m surprised at how easy the combination of Flex 2 and AMFPHP 2 are to develop with. If I had tools like these when I was knocking out my first e-learning apps in 2001&#8230; well probably nothing would be different, but it sure would&#8217;ve been easier. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Remember a few months back when I wrote about QA? I got a QA entry linking to a database working right out of Articulate Presenter as a tool in the upper right-hand corner. Honestly, it&#8217;s just a link to a URL, so it could be linked to anything, but the point is I have it working out of Articulate, using the LMS to provide your name when you enter a bug and Articulate to auto-fill the slide number you&#8217;re on, so all you have to do is tag what the problem is with keywords and then write a detailed description of the problem, and submit. The last week or two, I&#8217;ve been working on the management system to handle all that QA data, and I&#8217;m using it as an excuse to learn Flex 2 and AMFPHP 2.0 (currently in 1.9 beta 2). It&#8217;s fast, it&#8217;s effective, it&#8217;s efficient, it&#8217;s clean and neat &#8212; I&#8217;m surprised at how easy the combination of Flex 2 and AMFPHP 2 are to develop with. If I had tools like these when I was knocking out my first e-learning apps in 2001&#8230; well probably nothing would be different, but it sure would&#8217;ve been easier. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
