<?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: Some thoughts after watching an AJAX FABridge Flex demo</title>
	<atom:link href="http://flexblog.faratasystems.com/2006/10/17/some-thoughts-after-watching-an-ajax-fabridge-flex-demo/feed" rel="self" type="application/rss+xml" />
	<link>http://flexblog.faratasystems.com/2006/10/17/some-thoughts-after-watching-an-ajax-fabridge-flex-demo</link>
	<description>A blog about our experience with Adobe Flex</description>
	<lastBuildDate>Tue, 31 Jan 2012 19:52:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Yakov Fain</title>
		<link>http://flexblog.faratasystems.com/2006/10/17/some-thoughts-after-watching-an-ajax-fabridge-flex-demo/comment-page-1#comment-60</link>
		<dc:creator>Yakov Fain</dc:creator>
		<pubDate>Wed, 18 Oct 2006 10:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://flexblog.faratasystems.com/?p=101#comment-60</guid>
		<description>This particular demo should have been clearly marked with a banner stating &quot;Guys, do it this way only if you absolutely have to, because Joe Shmo from the department XYZ has already AJAX app and this is the only way to get Flex in the door&quot;. But it was not done this way, so people may have an impression that ths is the way to write Web applications where AJAX and Flex live happily ever after. This demo sends the following message:&quot;Guys, purchase our beautiful AJAX data grid, and you&#039;ll be able to create applications than can talk to Flex charting component&quot;, which is wrong.

How long do you think it would take to replace in this demo the AJAX data grid with the Flex one? Less than a day including QA. And this is the message people should deliver to   Joe Shmo: &quot;Just give us your AJAX applicaition, and we&#039;ll port whatever we can to Flex, leaving existing  complex AJAX components in place...for now&quot;.
FABridge is Adobe&#039;s marketing trick to show to the rest of the world that it can work with AJAX, which is enjoing lots of undeserved attention in the industry this year.  Hopefully the situation will change a year from now.</description>
		<content:encoded><![CDATA[<p>This particular demo should have been clearly marked with a banner stating &#8220;Guys, do it this way only if you absolutely have to, because Joe Shmo from the department XYZ has already AJAX app and this is the only way to get Flex in the door&#8221;. But it was not done this way, so people may have an impression that ths is the way to write Web applications where AJAX and Flex live happily ever after. This demo sends the following message:&#8221;Guys, purchase our beautiful AJAX data grid, and you&#8217;ll be able to create applications than can talk to Flex charting component&#8221;, which is wrong.</p>
<p>How long do you think it would take to replace in this demo the AJAX data grid with the Flex one? Less than a day including QA. And this is the message people should deliver to   Joe Shmo: &#8220;Just give us your AJAX applicaition, and we&#8217;ll port whatever we can to Flex, leaving existing  complex AJAX components in place&#8230;for now&#8221;.<br />
FABridge is Adobe&#8217;s marketing trick to show to the rest of the world that it can work with AJAX, which is enjoing lots of undeserved attention in the industry this year.  Hopefully the situation will change a year from now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Dowdell</title>
		<link>http://flexblog.faratasystems.com/2006/10/17/some-thoughts-after-watching-an-ajax-fabridge-flex-demo/comment-page-1#comment-59</link>
		<dc:creator>John Dowdell</dc:creator>
		<pubDate>Wed, 18 Oct 2006 04:20:27 +0000</pubDate>
		<guid isPermaLink="false">http://flexblog.faratasystems.com/?p=101#comment-59</guid>
		<description>&lt;em&gt;&quot;if I’m planning to pass data to Flex components anyway, why on Earth not just use Flex Data Grid in the first place?&quot;&lt;/em&gt;

Sure, in your situation, do that.  

I think these examples show that, even if you mainly work in JavaScript, then this Flex technology is accessible, practical, and useful today too. It builds the base of support, makes everybody more successful.

But if you&#039;re already comfortable with Flex, then your costs are much cheaper and you can do even more, agreed.

jd</description>
		<content:encoded><![CDATA[<p><em>&#8220;if I’m planning to pass data to Flex components anyway, why on Earth not just use Flex Data Grid in the first place?&#8221;</em></p>
<p>Sure, in your situation, do that.  </p>
<p>I think these examples show that, even if you mainly work in JavaScript, then this Flex technology is accessible, practical, and useful today too. It builds the base of support, makes everybody more successful.</p>
<p>But if you&#8217;re already comfortable with Flex, then your costs are much cheaper and you can do even more, agreed.</p>
<p>jd</p>
]]></content:encoded>
	</item>
</channel>
</rss>

