<?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 for Windows Phone</title>
	<atom:link href="http://www.winphone.ca/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.winphone.ca</link>
	<description>Windows Phone 7 News</description>
	<lastBuildDate>Thu, 17 Feb 2011 16:32:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on High Performance Progress Bar for Windows Phone by Jan Slodicka</title>
		<link>http://www.winphone.ca/articles/progress-bar/#comment-6</link>
		<dc:creator>Jan Slodicka</dc:creator>
		<pubDate>Thu, 17 Feb 2011 16:32:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.winphone.ca/?p=217#comment-6</guid>
		<description>Bad performance of the standard ProgressBar is primarily caused by using Storyboard mechanism. Storyboard animations run on the high priority render thread and use up approx. 50% of the CPU resources. This cannot be solved and Wilcox&#039;s solution handles just some less important problems of the ProgressBar implementation. In fact, the only good (I mean from the performance point of view) solution has to avoid using Storyboard animations and use timer-based animations instead.

See &lt;a href=&quot;http://www.codeproject.com/KB/showcase/WP7-Animations.aspx&quot; title=&quot;Windows Phone 7 Animations&quot; rel=&quot;nofollow&quot;&gt; for more info - benchmarks, algorithms etc.</description>
		<content:encoded><![CDATA[<p>Bad performance of the standard ProgressBar is primarily caused by using Storyboard mechanism. Storyboard animations run on the high priority render thread and use up approx. 50% of the CPU resources. This cannot be solved and Wilcox&#8217;s solution handles just some less important problems of the ProgressBar implementation. In fact, the only good (I mean from the performance point of view) solution has to avoid using Storyboard animations and use timer-based animations instead.</p>
<p>See <a href="http://www.codeproject.com/KB/showcase/WP7-Animations.aspx" title="Windows Phone 7 Animations" rel="nofollow"> for more info &#8211; benchmarks, algorithms etc.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Windows Phone Developer Tools January 2011 Update by Paula</title>
		<link>http://www.winphone.ca/articles/january-2011-update/#comment-1</link>
		<dc:creator>Paula</dc:creator>
		<pubDate>Mon, 07 Feb 2011 15:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.winphone.ca/?p=214#comment-1</guid>
		<description>Windows Phone 7 developer tools update today!  Copy and paste and a few other interesting items... head on over to App Hub to download!</description>
		<content:encoded><![CDATA[<p>Windows Phone 7 developer tools update today!  Copy and paste and a few other interesting items&#8230; head on over to App Hub to download!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: basic
Object Caching 198/215 objects using disk: basic

Served from: www.winphone.ca @ 2012-02-23 02:46:41 -->
