<?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: Thinking Declaratively with MXML</title>
	<atom:link href="http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/</link>
	<description>On the desktop, on the web, on the device ... On the Platform</description>
	<pubDate>Tue,  6 Jan 2009 21:37:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Simon G.</title>
		<link>http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-42221</link>
		<dc:creator>Simon G.</dc:creator>
		<pubDate>Sat, 17 May 2008 11:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-42221</guid>
		<description>Thanks Kevin Hoyt for this update!

Simon G.</description>
		<content:encoded><![CDATA[<p>Thanks Kevin Hoyt for this update!</p>
<p>Simon G.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mrinal Wadhwa</title>
		<link>http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-21441</link>
		<dc:creator>Mrinal Wadhwa</dc:creator>
		<pubDate>Mon, 28 Jan 2008 20:34:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-21441</guid>
		<description>It'll be a while before Flex 4 comes out and we get MXMLG but lately I have fallen in complete and utter love with degrafa.

Over the past month, I've been writing all my skins in mxml with degrafa and using markup instead of ActionScript makes the code so easy, intuitive, elegant and beautiful.   

Check this out and you'll know what I mean 

http://samples.degrafa.com/SphereSkinSample/SphereSkinSample.html</description>
		<content:encoded><![CDATA[<p>It&#8217;ll be a while before Flex 4 comes out and we get MXMLG but lately I have fallen in complete and utter love with degrafa.</p>
<p>Over the past month, I&#8217;ve been writing all my skins in mxml with degrafa and using markup instead of ActionScript makes the code so easy, intuitive, elegant and beautiful.   </p>
<p>Check this out and you&#8217;ll know what I mean </p>
<p><a href="http://samples.degrafa.com/SphereSkinSample/SphereSkinSample.html" rel="nofollow">http://samples.degrafa.com/SphereSkinSample/SphereSkinSample.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abdul Qabiz</title>
		<link>http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-21428</link>
		<dc:creator>Abdul Qabiz</dc:creator>
		<pubDate>Mon, 28 Jan 2008 17:57:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-21428</guid>
		<description>Hi Kevin,

As usual, a nice post and I also learnt more from this.

I have been doing some work using html/css/javascript and been following semantic-html and Layer Semantic Markup approach.

Just wondering, how would you thing semantic in context of mxml? MXML is very powerful because you can have structure as well as style/effects within in it? That surely also causes the bad-apps/design, if best-practices are not considered.

I have been thinking, how things should have been designed so that RIA applications developed using MXML/ActionScript/CSS can be progressively enhanced or gracefully degraded (for FlashLite etc).

For example: If there were a subset of MXML to represent semantic/structure of application, another subset to add presentation (CSS is there but limited in some sense) and last subset to add behavior/actions using actionscript.. 

It would have been easier to run RIAs on FlashLite by just taking care of presentation and actionscript... Think each part linked as different swfs?

I might not be making sense, just looking at standards already established and trying to draw some parallels... How can we make one app that works on most of the devices...

Flex framework needs to separate entire styles related stuff from it's component, it would become lighter and more flexible?

I hope, you get the sense... Since you are into both worlds (AJAX/DHTML and Flex), would love to hear your thoughts as a comment or new post :-)

Thanks

-abdul</description>
		<content:encoded><![CDATA[<p>Hi Kevin,</p>
<p>As usual, a nice post and I also learnt more from this.</p>
<p>I have been doing some work using html/css/javascript and been following semantic-html and Layer Semantic Markup approach.</p>
<p>Just wondering, how would you thing semantic in context of mxml? MXML is very powerful because you can have structure as well as style/effects within in it? That surely also causes the bad-apps/design, if best-practices are not considered.</p>
<p>I have been thinking, how things should have been designed so that RIA applications developed using MXML/ActionScript/CSS can be progressively enhanced or gracefully degraded (for FlashLite etc).</p>
<p>For example: If there were a subset of MXML to represent semantic/structure of application, another subset to add presentation (CSS is there but limited in some sense) and last subset to add behavior/actions using actionscript.. </p>
<p>It would have been easier to run RIAs on FlashLite by just taking care of presentation and actionscript&#8230; Think each part linked as different swfs?</p>
<p>I might not be making sense, just looking at standards already established and trying to draw some parallels&#8230; How can we make one app that works on most of the devices&#8230;</p>
<p>Flex framework needs to separate entire styles related stuff from it&#8217;s component, it would become lighter and more flexible?</p>
<p>I hope, you get the sense&#8230; Since you are into both worlds (AJAX/DHTML and Flex), would love to hear your thoughts as a comment or new post <img src='http://blog.kevinhoyt.org/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Thanks</p>
<p>-abdul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Hoyt</title>
		<link>http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-20260</link>
		<dc:creator>Kevin Hoyt</dc:creator>
		<pubDate>Tue, 15 Jan 2008 22:49:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-20260</guid>
		<description>Whoops!

The code in the article has been updated.

Thanks,
Kevin</description>
		<content:encoded><![CDATA[<p>Whoops!</p>
<p>The code in the article has been updated.</p>
<p>Thanks,<br />
Kevin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Branam</title>
		<link>http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-20254</link>
		<dc:creator>Jonathan Branam</dc:creator>
		<pubDate>Tue, 15 Jan 2008 21:47:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kevinhoyt.org/2008/01/15/thinking-declaratively-with-mxml/#comment-20254</guid>
		<description>I think the adding columns example is incorrect. You can't just myGrid.columns.push(...) because the accessor on columns returns a copy of the Array. You need to build another array and then assign it over the columns array.

var col:Array = myGrid.columns;
col.push( col );
myGrid.columns = col;</description>
		<content:encoded><![CDATA[<p>I think the adding columns example is incorrect. You can&#8217;t just myGrid.columns.push(&#8230;) because the accessor on columns returns a copy of the Array. You need to build another array and then assign it over the columns array.</p>
<p>var col:Array = myGrid.columns;<br />
col.push( col );<br />
myGrid.columns = col;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
