<?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: Flash Player content, Mouse Events, and Touch input</title>
	<atom:link href="http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/</link>
	<description>code = joy</description>
	<lastBuildDate>Fri, 27 Aug 2010 13:07:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Big Orange Software Blog &#187; Designing for mobile touch devices &#8211; learning from YouTube</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-2/#comment-23668</link>
		<dc:creator>Big Orange Software Blog &#187; Designing for mobile touch devices &#8211; learning from YouTube</dc:creator>
		<pubDate>Fri, 13 Aug 2010 16:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-23668</guid>
		<description>[...] User inputs need to be large enough to be used, but also ones that don&#8217;t need the non-existant hover state [...]</description>
		<content:encoded><![CDATA[<p>[...] User inputs need to be large enough to be used, but also ones that don&#8217;t need the non-existant hover state [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top Flash Misperceptions : Flash cannot run on touch devices at Mike Chambers</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-2/#comment-21909</link>
		<dc:creator>Top Flash Misperceptions : Flash cannot run on touch devices at Mike Chambers</dc:creator>
		<pubDate>Wed, 12 May 2010 17:47:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-21909</guid>
		<description>[...]  The myth began with the publishing of this article. I have already covered this topic in another post, but I wanted to address it again as it seems to have spread [...]</description>
		<content:encoded><![CDATA[<p>[...]  The myth began with the publishing of this article. I have already covered this topic in another post, but I wanted to address it again as it seems to have spread [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Johnson</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-2/#comment-21635</link>
		<dc:creator>James Johnson</dc:creator>
		<pubDate>Wed, 05 May 2010 15:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-21635</guid>
		<description>Touch screen problems are not flash specific.

Mouse overs are usually just aux UI augmentation (highlighting touchability).

Interfaces that allow drag and drop by trackin mouse down move up events have problems on iPhone and other
UIs that capture these events for their own use (scrolling)!  So the trick is how control who consumes a click drag event OS vs APP.  IF bubbling events from APP to OS then APP can INTERFEAR with scrolling OH NO.  If OS Consumes it (iPhone) then you cant drag your objects around the page!  There is
not hardware limitation only a limitation in Apples embrace of the free market.  Web Apps should be able to get tese messages first.  You want quality control, you dont need a single point of dist to do it, you only need certs. Users decide what they run.  You only need a good power tracking monitor in the OS to highlight which apps use what amount of power and let the consumer decide again. I am tired.


Apple is the perfect smug storm. Hackers fix all.</description>
		<content:encoded><![CDATA[<p>Touch screen problems are not flash specific.</p>
<p>Mouse overs are usually just aux UI augmentation (highlighting touchability).</p>
<p>Interfaces that allow drag and drop by trackin mouse down move up events have problems on iPhone and other<br />
UIs that capture these events for their own use (scrolling)!  So the trick is how control who consumes a click drag event OS vs APP.  IF bubbling events from APP to OS then APP can INTERFEAR with scrolling OH NO.  If OS Consumes it (iPhone) then you cant drag your objects around the page!  There is<br />
not hardware limitation only a limitation in Apples embrace of the free market.  Web Apps should be able to get tese messages first.  You want quality control, you dont need a single point of dist to do it, you only need certs. Users decide what they run.  You only need a good power tracking monitor in the OS to highlight which apps use what amount of power and let the consumer decide again. I am tired.</p>
<p>Apple is the perfect smug storm. Hackers fix all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: André Gil&#39;s Blog &#187; Steve Jobs: From Genius to&#8230; Crazy and Liar?</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-2/#comment-21527</link>
		<dc:creator>André Gil&#39;s Blog &#187; Steve Jobs: From Genius to&#8230; Crazy and Liar?</dc:creator>
		<pubDate>Fri, 30 Apr 2010 02:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-21527</guid>
		<description>[...] Chambers already proved that most Mouse Event from Flash works fine on the iPhone. Even MOUSE_OVER and ROLL_OVER works perfectly! The only problems are with middle click, right [...]</description>
		<content:encoded><![CDATA[<p>[...] Chambers already proved that most Mouse Event from Flash works fine on the iPhone. Even MOUSE_OVER and ROLL_OVER works perfectly! The only problems are with middle click, right [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-2/#comment-21518</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 29 Apr 2010 18:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-21518</guid>
		<description>Great summary! Thanks! This again proves that Jobs is full of shit, and just want&#039;s to discredit Flash. It&#039;s a way of leading consumers away from the real issue why Apple does not want Flash on their devices. That issue is greed and the control-nazi stance of Apple.</description>
		<content:encoded><![CDATA[<p>Great summary! Thanks! This again proves that Jobs is full of shit, and just want&#8217;s to discredit Flash. It&#8217;s a way of leading consumers away from the real issue why Apple does not want Flash on their devices. That issue is greed and the control-nazi stance of Apple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PhysicalFoursquare &#8211; A Flash Player 10.1 Demo App Using the Foursquare API &#124; Ryan Stewart &#8211; Rich Internet Application Mountaineer</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-2/#comment-21421</link>
		<dc:creator>PhysicalFoursquare &#8211; A Flash Player 10.1 Demo App Using the Foursquare API &#124; Ryan Stewart &#8211; Rich Internet Application Mountaineer</dc:creator>
		<pubDate>Wed, 28 Apr 2010 07:15:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-21421</guid>
		<description>[...] content, tuning your code will be central to a good experience. Three, as Mike Chambers showed, hover content works, but I found it kind of annoying. The way it&#8217;s currently set up, the hover event fires after [...]</description>
		<content:encoded><![CDATA[<p>[...] content, tuning your code will be central to a good experience. Three, as Mike Chambers showed, hover content works, but I found it kind of annoying. The way it&#8217;s currently set up, the hover event fires after [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: toolbear74</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-1/#comment-19092</link>
		<dc:creator>toolbear74</dc:creator>
		<pubDate>Tue, 06 Apr 2010 16:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-19092</guid>
		<description>@Mike,

Thanks for a hype-free treatment of the subject. You&#039;re responding to a sensationalized article, so I take the purpose of this article as combatting the spin surrounding the &quot;Flash can never work on touch devices&quot; meme. There&#039;s a kernel of truth to that meme if only it were stated differently.

-

Current Flash sites could never be made work well on any touchscreen device, and this cannot be solved by Apple, Adobe, or magical new hardware.

-

That&#039;s the sensational part. The article does elaborate on it, however. The point is that it&#039;s impractical to the point of being impossible to expect all sites which currently use Flash to be updated to work with touch devices.

As you pointed out this depends on a possibly false assumption, that most Flash content relies on hover in a primary way making that content unpleasant to use on a touch device (though not impossible as your videos have demonstrated). Dilger treats this assumption as true. You suggest it&#039;s false. Both assertions are subjective. Which position a reader believes is probably predicted by which side of the debate they wish to be on.

Personally I believe that it may be true that &quot;enough&quot; current flash content would be unpleasant to use. Ignoring this possibility is as much a mistake as blind faith that background apps are inherently superior while ignoring the challenges they present.

It&#039;s equally foolish to assume that because Flash may be a poor experience today on touch devices that that will be true for all time. Believing that blocking Flash promotes creation of touch compatible apps with newer tech (JS+Canvas) ignores that a similar &quot;clearing the field&quot; could be accomplished by only supporting a Flash version with acceptable levels of touch support.

I dislike Flash for the same reason I dislike Blu-ray. So the &quot;Flash can never work&quot; meme is an appealing siren&#039;s song. Thanks for cutting through the hype and taking a practitioners approach to the debate. Maybe you can wash away the hype from Dilger&#039;s article and find the kernels of truth. I feel that you&#039;ve glossed over some of that because you felt the need to defend Flash against inaccuracies in the article.</description>
		<content:encoded><![CDATA[<p>@Mike,</p>
<p>Thanks for a hype-free treatment of the subject. You&#8217;re responding to a sensationalized article, so I take the purpose of this article as combatting the spin surrounding the &#8220;Flash can never work on touch devices&#8221; meme. There&#8217;s a kernel of truth to that meme if only it were stated differently.</p>
<p>-</p>
<p>Current Flash sites could never be made work well on any touchscreen device, and this cannot be solved by Apple, Adobe, or magical new hardware.</p>
<p>-</p>
<p>That&#8217;s the sensational part. The article does elaborate on it, however. The point is that it&#8217;s impractical to the point of being impossible to expect all sites which currently use Flash to be updated to work with touch devices.</p>
<p>As you pointed out this depends on a possibly false assumption, that most Flash content relies on hover in a primary way making that content unpleasant to use on a touch device (though not impossible as your videos have demonstrated). Dilger treats this assumption as true. You suggest it&#8217;s false. Both assertions are subjective. Which position a reader believes is probably predicted by which side of the debate they wish to be on.</p>
<p>Personally I believe that it may be true that &#8220;enough&#8221; current flash content would be unpleasant to use. Ignoring this possibility is as much a mistake as blind faith that background apps are inherently superior while ignoring the challenges they present.</p>
<p>It&#8217;s equally foolish to assume that because Flash may be a poor experience today on touch devices that that will be true for all time. Believing that blocking Flash promotes creation of touch compatible apps with newer tech (JS+Canvas) ignores that a similar &#8220;clearing the field&#8221; could be accomplished by only supporting a Flash version with acceptable levels of touch support.</p>
<p>I dislike Flash for the same reason I dislike Blu-ray. So the &#8220;Flash can never work&#8221; meme is an appealing siren&#8217;s song. Thanks for cutting through the hype and taking a practitioners approach to the debate. Maybe you can wash away the hype from Dilger&#8217;s article and find the kernels of truth. I feel that you&#8217;ve glossed over some of that because you felt the need to defend Flash against inaccuracies in the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Would Flash work on a touch screen? &#171; flash 4 ipad</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-1/#comment-18762</link>
		<dc:creator>Would Flash work on a touch screen? &#171; flash 4 ipad</dc:creator>
		<pubDate>Tue, 09 Mar 2010 23:18:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-18762</guid>
		<description>[...] MikeChambers.com &#8211; on flash touch screen [...]</description>
		<content:encoded><![CDATA[<p>[...] MikeChambers.com &#8211; on flash touch screen [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Platform Shifts &#124; Ryan Stewart &#8211; Rich Internet Application Mountaineer</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-1/#comment-18722</link>
		<dc:creator>Platform Shifts &#124; Ryan Stewart &#8211; Rich Internet Application Mountaineer</dc:creator>
		<pubDate>Thu, 04 Mar 2010 23:45:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-18722</guid>
		<description>[...] of how much bigger a finger is than a mouse pointer and you&#8217;ll see the problems. I think the &#8220;hover&#8221; issues are completely overblown, but there is a big difference between Flash content in a mobile browser and Flash content in a web [...]</description>
		<content:encoded><![CDATA[<p>[...] of how much bigger a finger is than a mouse pointer and you&#8217;ll see the problems. I think the &#8220;hover&#8221; issues are completely overblown, but there is a big difference between Flash content in a mobile browser and Flash content in a web [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everything you thought about mobile Flash might be wrong</title>
		<link>http://www.mikechambers.com/blog/2010/02/22/flash-player-content-mouse-events-and-touch-input/comment-page-1/#comment-18643</link>
		<dc:creator>Everything you thought about mobile Flash might be wrong</dc:creator>
		<pubDate>Thu, 25 Feb 2010 00:57:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.mikechambers.com/blog/?p=1966#comment-18643</guid>
		<description>[...] top of this Mike Chambers recently debunked the idea that Flash wouldn’t work with touch screen devices, like the [...]</description>
		<content:encoded><![CDATA[<p>[...] top of this Mike Chambers recently debunked the idea that Flash wouldn’t work with touch screen devices, like the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
