<?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: Less reaching out and more touching</title>
	<atom:link href="http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/feed/" rel="self" type="application/rss+xml" />
	<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/</link>
	<description>A fun exploration of 2D binary fractal mapping</description>
	<lastBuildDate>Wed, 29 Jul 2009 05:46:47 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: subsume</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-18</link>
		<dc:creator>subsume</dc:creator>
		<pubDate>Thu, 05 Jul 2007 19:34:31 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-18</guid>
		<description>@JebusWankel

That gets to the heart of web app problems.  The site is not in control of the browser, and the iPhone in particular seems very locked down and unlikely to allow plugins.  Neither does the user control the site, so it ultimately falls on the site designer to keep interface changes in mind.  It&#039;s not just an iPhone/Safari issue, either.  As I said, touch screens aren&#039;t new, but I think the iPhone has set the stage for them to become more popular than ever, so it&#039;s generally a good idea to be mindful that the long-familiar mouse pointer is being depreciated.</description>
		<content:encoded><![CDATA[<p>@JebusWankel</p>
<p>That gets to the heart of web app problems.  The site is not in control of the browser, and the iPhone in particular seems very locked down and unlikely to allow plugins.  Neither does the user control the site, so it ultimately falls on the site designer to keep interface changes in mind.  It&#8217;s not just an iPhone/Safari issue, either.  As I said, touch screens aren&#8217;t new, but I think the iPhone has set the stage for them to become more popular than ever, so it&#8217;s generally a good idea to be mindful that the long-familiar mouse pointer is being depreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JebusWankel</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-17</link>
		<dc:creator>JebusWankel</dc:creator>
		<pubDate>Wed, 04 Jul 2007 22:41:57 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-17</guid>
		<description>Perhaps a safari browser plugin could better emulate a mouse for such sites. Touching with one finger could emulate a mouse hover and holding with the first while touching with a second finger could emulate a click.</description>
		<content:encoded><![CDATA[<p>Perhaps a safari browser plugin could better emulate a mouse for such sites. Touching with one finger could emulate a mouse hover and holding with the first while touching with a second finger could emulate a click.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aging like a not-so-fine wine &#171; The Ancient Game of Future Dominions</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-14</link>
		<dc:creator>Aging like a not-so-fine wine &#171; The Ancient Game of Future Dominions</dc:creator>
		<pubDate>Tue, 03 Jul 2007 04:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-14</guid>
		<description>[...] by the iPhone release alone. Even now we&#8217;re just starting to see scattered reports, just like we expected, of some Web 2.0 techniques not quite working on the [...]</description>
		<content:encoded><![CDATA[<p>[...] by the iPhone release alone. Even now we&#8217;re just starting to see scattered reports, just like we expected, of some Web 2.0 techniques not quite working on the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Countries in colors &#187; Blog Archive &#187; The do&#8217;s and dont&#8217;s of iPhone web development</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-12</link>
		<dc:creator>Countries in colors &#187; Blog Archive &#187; The do&#8217;s and dont&#8217;s of iPhone web development</dc:creator>
		<pubDate>Mon, 25 Jun 2007 13:16:27 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-12</guid>
		<description>[...] have thought that the advent of a finger control interface would spark so much debate? Others have debated at length on the implications of finger browsing, but the main conclusions may be summarized as [...]</description>
		<content:encoded><![CDATA[<p>[...] have thought that the advent of a finger control interface would spark so much debate? Others have debated at length on the implications of finger browsing, but the main conclusions may be summarized as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top Posts &#171; WordPress.com</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-8</link>
		<dc:creator>Top Posts &#171; WordPress.com</dc:creator>
		<pubDate>Sat, 23 Jun 2007 23:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-8</guid>
		<description>[...] Less reaching out and more touching It hasn&#8217;t escaped our attention that the Subsume alpha makes somewhat heavy use of &#8220;onmouse&#8221; events [&#8230;] [...]</description>
		<content:encoded><![CDATA[<p>[...] Less reaching out and more touching It hasn&#8217;t escaped our attention that the Subsume alpha makes somewhat heavy use of &#8220;onmouse&#8221; events [&#8230;] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: treyharrell</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-7</link>
		<dc:creator>treyharrell</dc:creator>
		<pubDate>Sat, 23 Jun 2007 18:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-7</guid>
		<description>I think that based on the specs that were leaked, the browser reports that it&#039;s a 480px width, which could screw up a lot of assumptions based on getting apps to scale to 100% in portrait view.

I&#039;ve decided that I&#039;m going to develop a second CSS layout for &lt;a href=&#039;http://www.iphone-geek.com&#039; rel=&quot;nofollow&quot;&gt;my site&lt;/a&gt; (done with the shameless plugs), but not launch it until I&#039;ve had a chance to test with the real deal. iPhoney is cool, but between the scrollbars and the fact that it allows rollovers, Flash and other stuff to load, it&#039;s not much use unless you&#039;re just testing user-agent redirection.

I&#039;m also what javascript hooks are available into the browser... not like you can test for mouse position, window position, hover, release, or a ton of other shortcuts web dev types use to make designs work (or quiet client demands, as the case is usually).

I&#039;ll definitely be running the browser and mail through a serious torture test next week, from a dev perspective.</description>
		<content:encoded><![CDATA[<p>I think that based on the specs that were leaked, the browser reports that it&#8217;s a 480px width, which could screw up a lot of assumptions based on getting apps to scale to 100% in portrait view.</p>
<p>I&#8217;ve decided that I&#8217;m going to develop a second CSS layout for <a href='http://www.iphone-geek.com' rel="nofollow">my site</a> (done with the shameless plugs), but not launch it until I&#8217;ve had a chance to test with the real deal. iPhoney is cool, but between the scrollbars and the fact that it allows rollovers, Flash and other stuff to load, it&#8217;s not much use unless you&#8217;re just testing user-agent redirection.</p>
<p>I&#8217;m also what javascript hooks are available into the browser&#8230; not like you can test for mouse position, window position, hover, release, or a ton of other shortcuts web dev types use to make designs work (or quiet client demands, as the case is usually).</p>
<p>I&#8217;ll definitely be running the browser and mail through a serious torture test next week, from a dev perspective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: subsume</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-6</link>
		<dc:creator>subsume</dc:creator>
		<pubDate>Sat, 23 Jun 2007 18:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-6</guid>
		<description>@treyharrell

The landscape/portrait is a really interesting issue when combined with what looks like a lack of scroll bars.  For the purposes of the game, we tried to take advantage of the mode changes by using them to show/hide extra player info, but I don&#039;t know what it&#039;ll mean for regular pages.  In the Apple videos I&#039;ve seen, pages appear to be rendered by some method at their &quot;largest&quot; size, and you&#039;d flick/zoom around using the iPhone screen as a kind of portal view on the page.  I have no idea what that is going to mean for elements that are sized relatively.  What does it mean to say something has 50% width when there is no window to size it relative to?  I also wonder how things like CSS position:fixed is going to get handled.  We can only wait and see on those issues, I guess, but taking a closer look at how mousing around is handled is something a web designer could look at before the 29th.</description>
		<content:encoded><![CDATA[<p>@treyharrell</p>
<p>The landscape/portrait is a really interesting issue when combined with what looks like a lack of scroll bars.  For the purposes of the game, we tried to take advantage of the mode changes by using them to show/hide extra player info, but I don&#8217;t know what it&#8217;ll mean for regular pages.  In the Apple videos I&#8217;ve seen, pages appear to be rendered by some method at their &#8220;largest&#8221; size, and you&#8217;d flick/zoom around using the iPhone screen as a kind of portal view on the page.  I have no idea what that is going to mean for elements that are sized relatively.  What does it mean to say something has 50% width when there is no window to size it relative to?  I also wonder how things like CSS position:fixed is going to get handled.  We can only wait and see on those issues, I guess, but taking a closer look at how mousing around is handled is something a web designer could look at before the 29th.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: treyharrell</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-5</link>
		<dc:creator>treyharrell</dc:creator>
		<pubDate>Sat, 23 Jun 2007 16:07:27 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-5</guid>
		<description>I&#039;ve got an article I wrote last week regarding &lt;a href=&quot;http://www.iphone-geek.com/2007/06/17/get-developing-iphone-browser-interaction-assumptions/&quot; rel=&quot;nofollow&quot;&gt;development and interaction considerations for the iPhone&lt;/a&gt;. 

Hover interactions are gotchas, and also that the user has the choice if she wants to be viewing in landscape or portrait mode and the site should degrade properly for both.

I&#039;ve also got a trivial little PHP function on there that sniffs user agent, because I believe we should reserve the media=&quot;mobile&quot; for other, dumber devices to use that are closer to a WAP browser.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve got an article I wrote last week regarding <a href="http://www.iphone-geek.com/2007/06/17/get-developing-iphone-browser-interaction-assumptions/" rel="nofollow">development and interaction considerations for the iPhone</a>. </p>
<p>Hover interactions are gotchas, and also that the user has the choice if she wants to be viewing in landscape or portrait mode and the site should degrade properly for both.</p>
<p>I&#8217;ve also got a trivial little PHP function on there that sniffs user agent, because I believe we should reserve the media=&#8221;mobile&#8221; for other, dumber devices to use that are closer to a WAP browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Fitzsimons</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-4</link>
		<dc:creator>Nick Fitzsimons</dc:creator>
		<pubDate>Sat, 23 Jun 2007 15:43:28 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-4</guid>
		<description>Assuming the use of a mouse has long been recognised as a bad idea, in that it discriminates against those unable to use one. The W3C&#039;s &lt;a href=&quot;http://www.w3.org/TR/WCAG10/#gl-device-independence&quot; rel=&quot;nofollow&quot;&gt;WCAG 1.0 points out that&lt;/a&gt; &quot;the user may interact with the user agent or document with a preferred input (or output) device -- mouse, keyboard, voice, head wand, or other.&quot; Hopefully interfaces such as the iPhone&#039;s will make web developers more aware of the need to make content accessible via many different modes of interaction.</description>
		<content:encoded><![CDATA[<p>Assuming the use of a mouse has long been recognised as a bad idea, in that it discriminates against those unable to use one. The W3C&#8217;s <a href="http://www.w3.org/TR/WCAG10/#gl-device-independence" rel="nofollow">WCAG 1.0 points out that</a> &#8220;the user may interact with the user agent or document with a preferred input (or output) device &#8212; mouse, keyboard, voice, head wand, or other.&#8221; Hopefully interfaces such as the iPhone&#8217;s will make web developers more aware of the need to make content accessible via many different modes of interaction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: subsume</title>
		<link>http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-3</link>
		<dc:creator>subsume</dc:creator>
		<pubDate>Sat, 23 Jun 2007 09:56:42 +0000</pubDate>
		<guid isPermaLink="false">http://subsume.wordpress.com/2007/06/19/less-reaching-out-and-more-touching/#comment-3</guid>
		<description>I must have missed that; do you have a link to the video on Apple&#039;s site where that happens?  Still, even if Steve mentioned it in passing, it hasn&#039;t received very much attention by anyone else.  Just like I can&#039;t recall Steve saying anything about it, I can&#039;t recall any mention in the hundreds (or thousands) of news stories that have covered the iPhone.</description>
		<content:encoded><![CDATA[<p>I must have missed that; do you have a link to the video on Apple&#8217;s site where that happens?  Still, even if Steve mentioned it in passing, it hasn&#8217;t received very much attention by anyone else.  Just like I can&#8217;t recall Steve saying anything about it, I can&#8217;t recall any mention in the hundreds (or thousands) of news stories that have covered the iPhone.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
