<?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: It&#8217;s not so smooth. T-Mobile G1 multi-touch video demo</title>
	<atom:link href="http://www.winandmac.com/news/its-not-so-smooth-t-mobile-g1-multi-touch-video-demo/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.winandmac.com/news/its-not-so-smooth-t-mobile-g1-multi-touch-video-demo/</link>
	<description>tech news that you want</description>
	<lastBuildDate>Fri, 12 Mar 2010 01:24:56 +0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: RyeBrye</title>
		<link>http://www.winandmac.com/news/its-not-so-smooth-t-mobile-g1-multi-touch-video-demo/comment-page-1/#comment-67575</link>
		<dc:creator>RyeBrye</dc:creator>
		<pubDate>Sun, 23 Nov 2008 20:30:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.winandmac.com/?p=5587#comment-67575</guid>
		<description>The main reason it is slow is because of how the demo hack was implemented - I&#039;ve got one thread that is basically constantly polling a device file to look for the touchscreen output getting dumped... the reason I did it that way was to just get a demo built without having to do the hard work of properly putting things in place in the framework to do it.

I have no reason to believe it will be slow once it is properly built - If anything, the fact that this ghetto end-run hack around the event system actually works reasonably smoothly is actually quite impressive.

I think with a few interested developers helping, things could move forward relatively quickly.</description>
		<content:encoded><![CDATA[<p>The main reason it is slow is because of how the demo hack was implemented &#8211; I&#8217;ve got one thread that is basically constantly polling a device file to look for the touchscreen output getting dumped&#8230; the reason I did it that way was to just get a demo built without having to do the hard work of properly putting things in place in the framework to do it.</p>
<p>I have no reason to believe it will be slow once it is properly built &#8211; If anything, the fact that this ghetto end-run hack around the event system actually works reasonably smoothly is actually quite impressive.</p>
<p>I think with a few interested developers helping, things could move forward relatively quickly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
