<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Silverlight: GridSplitter with a collapse button</title>
	<atom:link href="http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/feed/" rel="self" type="application/rss+xml" />
	<link>http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/</link>
	<description>Toxicated Flex/Silverlight Blog</description>
	<lastBuildDate>Tue, 10 Nov 2009 18:27:14 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brad</title>
		<link>http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/#comment-205</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Mon, 30 Mar 2009 03:12:44 +0000</pubDate>
		<guid isPermaLink="false">http://shemesh.wordpress.com/?p=48#comment-205</guid>
		<description>Coming from Flex, WPF has quite the learning curve. I can see where they are coming from, but some things are a little insane.

Flex (Flash) comes from an animation root to development. WPF comes from development to design.

MS needs to improve the tools if they ever expect to get a wide following from designers.</description>
		<content:encoded><![CDATA[<p>Coming from Flex, WPF has quite the learning curve. I can see where they are coming from, but some things are a little insane.</p>
<p>Flex (Flash) comes from an animation root to development. WPF comes from development to design.</p>
<p>MS needs to improve the tools if they ever expect to get a wide following from designers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shemesh</title>
		<link>http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/#comment-115</link>
		<dc:creator>shemesh</dc:creator>
		<pubDate>Wed, 14 Jan 2009 08:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://shemesh.wordpress.com/?p=48#comment-115</guid>
		<description>scott,
as i m a Flex developer in the last 3 years and web developer for the 3 years before i DO have a clue of what are the differences!
my opinion is based upon hands-on experience.
i do not care if you call it CSS or whatever - styling Silverlight is a very unpleasant, unfriendly job.
i m ending up with XAML pages that have HUNDREDS of lines just to change some minor property (try styling a DataGrid / ListBox)
and yes - CSS is much much more pleasent to work with. have you ever developed Flex applications?

and i still haven&#039;t said anything about SL compiling with errors, very weird runtime errors messages, and above all - performance issues.
most of the time i find myself writing workarounds for bugs/holes/walls i encounter.
Silverlight have a long way to go before it is matured into a real framework one can count on!</description>
		<content:encoded><![CDATA[<p>scott,<br />
as i m a Flex developer in the last 3 years and web developer for the 3 years before i DO have a clue of what are the differences!<br />
my opinion is based upon hands-on experience.<br />
i do not care if you call it CSS or whatever &#8211; styling Silverlight is a very unpleasant, unfriendly job.<br />
i m ending up with XAML pages that have HUNDREDS of lines just to change some minor property (try styling a DataGrid / ListBox)<br />
and yes &#8211; CSS is much much more pleasent to work with. have you ever developed Flex applications?</p>
<p>and i still haven&#8217;t said anything about SL compiling with errors, very weird runtime errors messages, and above all &#8211; performance issues.<br />
most of the time i find myself writing workarounds for bugs/holes/walls i encounter.<br />
Silverlight have a long way to go before it is matured into a real framework one can count on!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scott</title>
		<link>http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/#comment-114</link>
		<dc:creator>scott</dc:creator>
		<pubDate>Tue, 13 Jan 2009 15:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://shemesh.wordpress.com/?p=48#comment-114</guid>
		<description>&quot;SL have a weird way for styling - why not use the industry standard CSS.&quot;

Because it&#039;s NOT HTML? Because it&#039;s not a web document?

When I hear people compare XAML to HTML and CSS and lament how XAML is not like HTML and CSS, I can&#039;t help but think they don&#039;t have a grasp of what XAML actually is. XAML is a way to describe user interfaces or hierarchies of objects. It allows you to seperate presentation from logic. Everything that I describe in XAML is turned into a real object. I can create the exact same user interface by creating objects in the code-behind files. Including the styling of obejcts (Brush with Color.Red). This is NOT what HTML does or what it was meant for.

Also, the databinding in WPF includes binding of properties between objects, so if that is missing in SL don&#039;t be sure it won&#039;t show up later.

I recommend getting a good WPF book so you can fully understand what XAML is. Something like &quot;Windows Presentation Foundation Unleashed&quot; is an easy read. Once you fully understand what XAML is you will no longer wonder why you can use what is essentially an unreleated technology meant to style web documents (CSS).</description>
		<content:encoded><![CDATA[<p>&#8220;SL have a weird way for styling &#8211; why not use the industry standard CSS.&#8221;</p>
<p>Because it&#8217;s NOT HTML? Because it&#8217;s not a web document?</p>
<p>When I hear people compare XAML to HTML and CSS and lament how XAML is not like HTML and CSS, I can&#8217;t help but think they don&#8217;t have a grasp of what XAML actually is. XAML is a way to describe user interfaces or hierarchies of objects. It allows you to seperate presentation from logic. Everything that I describe in XAML is turned into a real object. I can create the exact same user interface by creating objects in the code-behind files. Including the styling of obejcts (Brush with Color.Red). This is NOT what HTML does or what it was meant for.</p>
<p>Also, the databinding in WPF includes binding of properties between objects, so if that is missing in SL don&#8217;t be sure it won&#8217;t show up later.</p>
<p>I recommend getting a good WPF book so you can fully understand what XAML is. Something like &#8220;Windows Presentation Foundation Unleashed&#8221; is an easy read. Once you fully understand what XAML is you will no longer wonder why you can use what is essentially an unreleated technology meant to style web documents (CSS).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shemesh</title>
		<link>http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/#comment-97</link>
		<dc:creator>shemesh</dc:creator>
		<pubDate>Wed, 19 Nov 2008 15:19:19 +0000</pubDate>
		<guid isPermaLink="false">http://shemesh.wordpress.com/?p=48#comment-97</guid>
		<description>well...
in SL everything is longer, if in Flex i needed 2 lines to write something in SL it takes about 10 lines of code to do the same.
SL is kind of &#039;empty&#039; if you need something you most likely need to develop it yourself.
SL layouting is not nice! it does not have any work with dimensions in percentage. this is ending us doing all the size-change calculations.
SL have a weird way for styling - why not use the industry standard CSS.
SL cannot do binding to UI objects properties (e.g. u cannot bind a Canvas width to a Slider value).
SL does not know what is bitmap, with all that implicit.


i can find more, but i m not here to complain.
all-in-all: Flex+AS3 is much more friendly to the developer.</description>
		<content:encoded><![CDATA[<p>well&#8230;<br />
in SL everything is longer, if in Flex i needed 2 lines to write something in SL it takes about 10 lines of code to do the same.<br />
SL is kind of &#8216;empty&#8217; if you need something you most likely need to develop it yourself.<br />
SL layouting is not nice! it does not have any work with dimensions in percentage. this is ending us doing all the size-change calculations.<br />
SL have a weird way for styling &#8211; why not use the industry standard CSS.<br />
SL cannot do binding to UI objects properties (e.g. u cannot bind a Canvas width to a Slider value).<br />
SL does not know what is bitmap, with all that implicit.</p>
<p>i can find more, but i m not here to complain.<br />
all-in-all: Flex+AS3 is much more friendly to the developer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danijel</title>
		<link>http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/#comment-96</link>
		<dc:creator>Danijel</dc:creator>
		<pubDate>Wed, 19 Nov 2008 10:52:34 +0000</pubDate>
		<guid isPermaLink="false">http://shemesh.wordpress.com/?p=48#comment-96</guid>
		<description>I am also curious to hear why &quot;Silverlight is much more hard-to-handle then Flex&quot; from perspective of someone who already used Flex?</description>
		<content:encoded><![CDATA[<p>I am also curious to hear why &#8220;Silverlight is much more hard-to-handle then Flex&#8221; from perspective of someone who already used Flex?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 2008 November 19 - Links for today &#171; My (almost) Daily Links</title>
		<link>http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/#comment-95</link>
		<dc:creator>2008 November 19 - Links for today &#171; My (almost) Daily Links</dc:creator>
		<pubDate>Wed, 19 Nov 2008 09:22:01 +0000</pubDate>
		<guid isPermaLink="false">http://shemesh.wordpress.com/?p=48#comment-95</guid>
		<description>[...] Shemesh with Silverlight: GridSplitter with a collapse button [...]</description>
		<content:encoded><![CDATA[<p>[...] Shemesh with Silverlight: GridSplitter with a collapse button [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fallon Massey</title>
		<link>http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/#comment-94</link>
		<dc:creator>Fallon Massey</dc:creator>
		<pubDate>Wed, 19 Nov 2008 08:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://shemesh.wordpress.com/?p=48#comment-94</guid>
		<description>You said,

&quot;Silverlight is much more hard-to-handle then Flex&quot;

I would like to know what you mean by that, just for comparison.  Were you a Flash/Flex developer before using silverlight?</description>
		<content:encoded><![CDATA[<p>You said,</p>
<p>&#8220;Silverlight is much more hard-to-handle then Flex&#8221;</p>
<p>I would like to know what you mean by that, just for comparison.  Were you a Flash/Flex developer before using silverlight?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Silverlight Cream for November 18, 2008 -- #431</title>
		<link>http://shemesh.wordpress.com/2008/11/18/silverlight-gridsplitter-with-a-collapse-button/#comment-93</link>
		<dc:creator>Silverlight Cream for November 18, 2008 -- #431</dc:creator>
		<pubDate>Tue, 18 Nov 2008 21:51:39 +0000</pubDate>
		<guid isPermaLink="false">http://shemesh.wordpress.com/?p=48#comment-93</guid>
		<description>[...] Silverlight: GridSplitter with a collapse button [...]</description>
		<content:encoded><![CDATA[<p>[...] Silverlight: GridSplitter with a collapse button [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
