<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What&#8217;s Next &#8211; the Road to Gibraltar 3.0</title>
	<atom:link href="http://rocksolid.gibraltarsoftware.com/development/whats-next-the-road-to-gibraltar-3-0/feed" rel="self" type="application/rss+xml" />
	<link>http://rocksolid.gibraltarsoftware.com/development/whats-next-the-road-to-gibraltar-3-0</link>
	<description>Notes from the folks behind Gibraltar Software</description>
	<lastBuildDate>Sat, 10 Dec 2011 21:22:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Reworking the Gibraltar AddIn API :: Rock Solid</title>
		<link>http://rocksolid.gibraltarsoftware.com/development/whats-next-the-road-to-gibraltar-3-0/comment-page-1#comment-505</link>
		<dc:creator>Reworking the Gibraltar AddIn API :: Rock Solid</dc:creator>
		<pubDate>Mon, 14 Jun 2010 04:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://rocksolid.gibraltarsoftware.com/?p=492#comment-505</guid>
		<description>[...] That said, it&#8217;s generally been my experience that no matter how good and diligent you are when designing an API you&#8217;ll inevitably find that you&#8217;ve missed the mark as soon as the first set of users start solving real problems with it.   So, you&#8217;ll want to leave room to redo and rethink your original approach before you&#8217;re married to it.  This is the major reason that we shipped Gibraltar 2.2.0 as a Beta back in early April with our first vision of a Gibraltar Add In API. [...]</description>
		<content:encoded><![CDATA[<p>[...] That said, it&#8217;s generally been my experience that no matter how good and diligent you are when designing an API you&#8217;ll inevitably find that you&#8217;ve missed the mark as soon as the first set of users start solving real problems with it.   So, you&#8217;ll want to leave room to redo and rethink your original approach before you&#8217;re married to it.  This is the major reason that we shipped Gibraltar 2.2.0 as a Beta back in early April with our first vision of a Gibraltar Add In API. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Extensible UI: Usability challenges and solutions :: Rock Solid</title>
		<link>http://rocksolid.gibraltarsoftware.com/development/whats-next-the-road-to-gibraltar-3-0/comment-page-1#comment-474</link>
		<dc:creator>Extensible UI: Usability challenges and solutions :: Rock Solid</dc:creator>
		<pubDate>Fri, 02 Apr 2010 04:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://rocksolid.gibraltarsoftware.com/?p=492#comment-474</guid>
		<description>[...] going to release a beta of Gibraltar 2.2 imminently.  We&#8217;re considering it a beta because of the new add-in API which we want to get a broader set of feedback on before we&#8217;re committed to its design.  The [...]</description>
		<content:encoded><![CDATA[<p>[...] going to release a beta of Gibraltar 2.2 imminently.  We&#8217;re considering it a beta because of the new add-in API which we want to get a broader set of feedback on before we&#8217;re committed to its design.  The [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unpredictable feature coolness :: Rock Solid</title>
		<link>http://rocksolid.gibraltarsoftware.com/development/whats-next-the-road-to-gibraltar-3-0/comment-page-1#comment-469</link>
		<dc:creator>Unpredictable feature coolness :: Rock Solid</dc:creator>
		<pubDate>Mon, 22 Mar 2010 19:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://rocksolid.gibraltarsoftware.com/?p=492#comment-469</guid>
		<description>[...] tray in our latest builds.  We added this feature originally to address a shortcoming:  With the new API for session analysis it&#8217;s really desirable to be able to leave a copy of Analyst running somewhere to make sure [...]</description>
		<content:encoded><![CDATA[<p>[...] tray in our latest builds.  We added this feature originally to address a shortcoming:  With the new API for session analysis it&#8217;s really desirable to be able to leave a copy of Analyst running somewhere to make sure [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

