<?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: Can Flex be Design Driven?	</title>
	<atom:link href="https://jessewarden.com/2006/06/can-flex-be-design-driven.html/feed" rel="self" type="application/rss+xml" />
	<link>https://jessewarden.com/2006/06/can-flex-be-design-driven.html</link>
	<description>Software &#124; Fitness &#124; Gaming</description>
	<lastBuildDate>Tue, 01 Aug 2006 09:42:20 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: nick		</title>
		<link>https://jessewarden.com/2006/06/can-flex-be-design-driven.html/comment-page-1#comment-3589</link>

		<dc:creator><![CDATA[nick]]></dc:creator>
		<pubDate>Tue, 01 Aug 2006 09:42:20 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1030#comment-3589</guid>

					<description><![CDATA[hey jesse - 
well i have to say i gave flex a really close look. as a mac user i installed parallels, bought xp pro and installed the flex trial. something about flex just doesnt ]]></description>
			<content:encoded><![CDATA[<p>hey jesse &#8211;<br />
well i have to say i gave flex a really close look. as a mac user i installed parallels, bought xp pro and installed the flex trial. something about flex just doesnt </p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kenny Bunch		</title>
		<link>https://jessewarden.com/2006/06/can-flex-be-design-driven.html/comment-page-1#comment-3588</link>

		<dc:creator><![CDATA[Kenny Bunch]]></dc:creator>
		<pubDate>Sat, 01 Jul 2006 05:26:04 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1030#comment-3588</guid>

					<description><![CDATA[PS. Remember that day when I was telling you where I thought MM would go with all their tools, player, etc. Interesting to see where they are at ;). What gets me know like I said is where they are going. I have high hopes.]]></description>
			<content:encoded><![CDATA[<p>PS. Remember that day when I was telling you where I thought MM would go with all their tools, player, etc. Interesting to see where they are at ;). What gets me know like I said is where they are going. I have high hopes.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kenny Bunch		</title>
		<link>https://jessewarden.com/2006/06/can-flex-be-design-driven.html/comment-page-1#comment-3587</link>

		<dc:creator><![CDATA[Kenny Bunch]]></dc:creator>
		<pubDate>Sat, 01 Jul 2006 05:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1030#comment-3587</guid>

					<description><![CDATA[Jesse,
Thanks for making the long trek into town. To your point, I would say currently Flex can be used with design to an extent. Theoretically you could create the same application you might create with Flash, design wise and all. However, it depends on how you are defining design. Like we talked about and I think you were able to explain, most of the applications you have been working on are very business based, form driven apps. These are perfect for Flex, and ridiculous for Flash. On the other hand, you have marketing/design apps. These are a different breed. To your example, X3 could be done in Flex, but should it? How long would it take in comparison to Flash? Flex is good with an existing component structure. You have elements you drag and drop in. In Flash, designers are creating the elements right there in the canvas, there vision (pixel by pixel) is translated directly. It is not you or I twisting their elements to work. To this point, both tools serve different needs. Both needs are valid, creating the need for the separate tools. I currently use both and love both.  You pick the tool that fits the job. Adobe has really moved in the right direction. Now I&#039;m interested to see what Appolo brings to the fold. My guess is a Mozilla based desktop engine.]]></description>
			<content:encoded><![CDATA[<p>Jesse,<br />
Thanks for making the long trek into town. To your point, I would say currently Flex can be used with design to an extent. Theoretically you could create the same application you might create with Flash, design wise and all. However, it depends on how you are defining design. Like we talked about and I think you were able to explain, most of the applications you have been working on are very business based, form driven apps. These are perfect for Flex, and ridiculous for Flash. On the other hand, you have marketing/design apps. These are a different breed. To your example, X3 could be done in Flex, but should it? How long would it take in comparison to Flash? Flex is good with an existing component structure. You have elements you drag and drop in. In Flash, designers are creating the elements right there in the canvas, there vision (pixel by pixel) is translated directly. It is not you or I twisting their elements to work. To this point, both tools serve different needs. Both needs are valid, creating the need for the separate tools. I currently use both and love both.  You pick the tool that fits the job. Adobe has really moved in the right direction. Now I&#8217;m interested to see what Appolo brings to the fold. My guess is a Mozilla based desktop engine.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Josh Tynjala		</title>
		<link>https://jessewarden.com/2006/06/can-flex-be-design-driven.html/comment-page-1#comment-3586</link>

		<dc:creator><![CDATA[Josh Tynjala]]></dc:creator>
		<pubDate>Sat, 01 Jul 2006 01:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1030#comment-3586</guid>

					<description><![CDATA[Tom has a good point. If properly skinned, you can work with the Flex framework, and no one will even recognize it. That&#039;s exciting. BUT, it&#039;s kind of heavy, and that means a long, boring download for a flashy entertainment site. That&#039;s not exciting. Flex is designed with bigger applications (with lots of opportunities for components) in mind. For an entertainment site, you&#039;d be better off finding something lighter if you want it based off basic components and views like that.]]></description>
			<content:encoded><![CDATA[<p>Tom has a good point. If properly skinned, you can work with the Flex framework, and no one will even recognize it. That&#8217;s exciting. BUT, it&#8217;s kind of heavy, and that means a long, boring download for a flashy entertainment site. That&#8217;s not exciting. Flex is designed with bigger applications (with lots of opportunities for components) in mind. For an entertainment site, you&#8217;d be better off finding something lighter if you want it based off basic components and views like that.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rahsun McAfee		</title>
		<link>https://jessewarden.com/2006/06/can-flex-be-design-driven.html/comment-page-1#comment-3585</link>

		<dc:creator><![CDATA[Rahsun McAfee]]></dc:creator>
		<pubDate>Fri, 30 Jun 2006 21:54:27 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/?p=1030#comment-3585</guid>

					<description><![CDATA[ummm...yeah .... I don&#039;t know. It&#039;s weird cause I have to be developer / designer most of the time. 

It took a while for me to get into a flow because usually I&#039;m a designer 1st then developer.

Most people might not agree, but I hate stuff that looks alike from the design perspective. I know it&#039;s more work, but I&#039;m usually thinking of how I can change a component visually as oppose to extending it&#039;s capabilities. 

I use RoR more and morenow and got in a conversation with another the other day who HATES Flash cause it&#039;s &#039;not open&#039; ummmmm....wtf!? I also run into many programmers who get excited because it works and says &#039;oh yeah, put some colors on that.&#039; ...ummm again WTF?!

After some time I believe that I probably start thinking design first these days. However not in the traditional sense of colors, fonts, etc.

I usually start with HOW do I want to visually represent something.  I want to get to prototype as soon as possible with basic layout and interaction functionality. From there if the back end has to be developed it can and if the front end has to be refined (fonts, colors, animations, etc.) then it can at the same time. 

Right now that &#039;thought&#039; process works better for me. Will it change, I don&#039;t know, maybe. However over time I&#039;ve realized that looking good&lt;b&gt; &lt;/b&gt;AND working good to me are &lt;b&gt;equally&lt;/b&gt; important.]]></description>
			<content:encoded><![CDATA[<p>ummm&#8230;yeah &#8230;. I don&#8217;t know. It&#8217;s weird cause I have to be developer / designer most of the time. </p>
<p>It took a while for me to get into a flow because usually I&#8217;m a designer 1st then developer.</p>
<p>Most people might not agree, but I hate stuff that looks alike from the design perspective. I know it&#8217;s more work, but I&#8217;m usually thinking of how I can change a component visually as oppose to extending it&#8217;s capabilities. </p>
<p>I use RoR more and morenow and got in a conversation with another the other day who HATES Flash cause it&#8217;s &#8216;not open&#8217; ummmmm&#8230;.wtf!? I also run into many programmers who get excited because it works and says &#8216;oh yeah, put some colors on that.&#8217; &#8230;ummm again WTF?!</p>
<p>After some time I believe that I probably start thinking design first these days. However not in the traditional sense of colors, fonts, etc.</p>
<p>I usually start with HOW do I want to visually represent something.  I want to get to prototype as soon as possible with basic layout and interaction functionality. From there if the back end has to be developed it can and if the front end has to be refined (fonts, colors, animations, etc.) then it can at the same time. </p>
<p>Right now that &#8216;thought&#8217; process works better for me. Will it change, I don&#8217;t know, maybe. However over time I&#8217;ve realized that looking good<b> </b>AND working good to me are <b>equally</b> important.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
