<?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: Goodbye WPTouch</title>
	<atom:link href="http://test.latko.org/?feed=rss2&#038;p=119" rel="self" type="application/rss+xml" />
	<link>http://test.latko.org/?p=119</link>
	<description>A Misanthropic Anthropoid With Something to Say</description>
	<lastBuildDate>Sun, 13 Nov 2022 02:54:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Latko</title>
		<link>http://test.latko.org/?p=119&#038;cpage=1#comment-10</link>
		<dc:creator>Chris Latko</dc:creator>
		<pubDate>Wed, 04 Feb 2009 16:56:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.latko.org/?p=119#comment-10</guid>
		<description>I think WPtouch is a great product. That&#039;s why I chose it over many alternate solutions. It does 95% percent of what I want it to do. I don&#039;t really care about losing the sidebars either.

I do a lot of reading on my iPhone and it has been increasingly frustrating to read boiled down iPhone templates and I just didn&#039;t want to inflict that on my users. I&#039;m not saying WPtouch is boiled down, but is a new interface forced on the user. Most of these other sites do not offer &quot;normal&quot; view as far as I can tell.

Also, as a frequent user of my own site (there is quite a bit of functionality behind the scenes) I was growing increasing frustrated with the process of changing to normal view to use these functions. Mobile Safari is not a paragon of stability, but 2.2.1 helped quite a bit, and is often purged of cookies due to crashes or resource overload. Once this happens, I get the default WPtouch mode.

I wanted to dive into your code to reverse the view mode, as you mentioned, but have other projects that take priority.

I have deactivated, not uninstalled your plugin, and will follow its progress. I look forward to your next version.</description>
		<content:encoded><![CDATA[<p>I think WPtouch is a great product. That&#8217;s why I chose it over many alternate solutions. It does 95% percent of what I want it to do. I don&#8217;t really care about losing the sidebars either.</p>
<p>I do a lot of reading on my iPhone and it has been increasingly frustrating to read boiled down iPhone templates and I just didn&#8217;t want to inflict that on my users. I&#8217;m not saying WPtouch is boiled down, but is a new interface forced on the user. Most of these other sites do not offer &#8220;normal&#8221; view as far as I can tell.</p>
<p>Also, as a frequent user of my own site (there is quite a bit of functionality behind the scenes) I was growing increasing frustrated with the process of changing to normal view to use these functions. Mobile Safari is not a paragon of stability, but 2.2.1 helped quite a bit, and is often purged of cookies due to crashes or resource overload. Once this happens, I get the default WPtouch mode.</p>
<p>I wanted to dive into your code to reverse the view mode, as you mentioned, but have other projects that take priority.</p>
<p>I have deactivated, not uninstalled your plugin, and will follow its progress. I look forward to your next version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Mugford</title>
		<link>http://test.latko.org/?p=119&#038;cpage=1#comment-9</link>
		<dc:creator>Dale Mugford</dc:creator>
		<pubDate>Wed, 04 Feb 2009 15:13:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.latko.org/?p=119#comment-9</guid>
		<description>I can understand your frustration, but we feel WPtouch solves that issue by allowing for the visitor to switch between the normal view of a website and WPtouch.

That way on a per user basis the choice can be made. The choice is saved as a cookie and thus when they return to visit your site they&#039;ll see your standard theme.

As for content, WPtouch doesn&#039;t remove your content, aside from sidebar content. The next version of WPtouch is even more powerful, and we&#039;ll consider the option to have visitors see your desktop theme first, and be given the chance to switch to WPtouch, instead of the other way around.</description>
		<content:encoded><![CDATA[<p>I can understand your frustration, but we feel WPtouch solves that issue by allowing for the visitor to switch between the normal view of a website and WPtouch.</p>
<p>That way on a per user basis the choice can be made. The choice is saved as a cookie and thus when they return to visit your site they&#8217;ll see your standard theme.</p>
<p>As for content, WPtouch doesn&#8217;t remove your content, aside from sidebar content. The next version of WPtouch is even more powerful, and we&#8217;ll consider the option to have visitors see your desktop theme first, and be given the chance to switch to WPtouch, instead of the other way around.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
