<?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: WPTouch iPhone Theme and the crippled translation</title>
	<atom:link href="http://www.code-styling.de/english/wptouch-iphone-theme-and-the-crippled-translation/feed" rel="self" type="application/rss+xml" />
	<link>http://www.code-styling.de/english/wptouch-iphone-theme-and-the-crippled-translation</link>
	<description>It's not a bug, it's always a feature.</description>
	<pubDate>Sat, 04 Feb 2012 05:31:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: sorin</title>
		<link>http://www.code-styling.de/english/wptouch-iphone-theme-and-the-crippled-translation#comment-1613</link>
		<dc:creator>sorin</dc:creator>
		<pubDate>Sun, 19 Sep 2010 11:38:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.code-styling.de/?p=1383#comment-1613</guid>
		<description>I fully understand the reasoning for creating a payed version but this looks as defective product management - why ? because it creates frustration for the users.

Probably this model will work until someone, frustrated by this business model, will create a real open-source project (whith community contributors with full access to a issue tracker and source control repository).

I checked the  comparison page from http://www.bravenewcode.com/products/wptouch-pro/ and it was enough to conclude that the model *very* closed:
* documentation only for paying customers 
* vip forum for paying customers, if you want to give them something add support. Limiting the access to a forum is just lame, and could be a way of hiding frustrations of paying customers.
* localization only in payed version, yep,... now hope to get translations from the community!

I know few other models that are more open: for example if you pay you get the new version upgrade automatically, free users are getting it with a delay of one month or more.</description>
		<content:encoded><![CDATA[<p>I fully understand the reasoning for creating a payed version but this looks as defective product management - why ? because it creates frustration for the users.</p>
<p>Probably this model will work until someone, frustrated by this business model, will create a real open-source project (whith community contributors with full access to a issue tracker and source control repository).</p>
<p>I checked the  comparison page from <a href="http://www.bravenewcode.com/products/wptouch-pro/" rel="nofollow">http://www.bravenewcode.com/products/wptouch-pro/</a> and it was enough to conclude that the model *very* closed:<br />
* documentation only for paying customers<br />
* vip forum for paying customers, if you want to give them something add support. Limiting the access to a forum is just lame, and could be a way of hiding frustrations of paying customers.<br />
* localization only in payed version, yep,&#8230; now hope to get translations from the community!</p>
<p>I know few other models that are more open: for example if you pay you get the new version upgrade automatically, free users are getting it with a delay of one month or more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale Mugford</title>
		<link>http://www.code-styling.de/english/wptouch-iphone-theme-and-the-crippled-translation#comment-1568</link>
		<dc:creator>Dale Mugford</dc:creator>
		<pubDate>Thu, 02 Sep 2010 23:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.code-styling.de/?p=1383#comment-1568</guid>
		<description>This article is flat out false. We never intentionally crippled it, ever. We responded to your request, and you seem to be a little hasty. 1.9.18 was already prepped by the time we released it. 

Please, relax. We're not obligated nor required to do anything for what we freely have offered to everyone. WPtouch has been downloaded over 1,000,000 times. We have a lot of support requests related to it, and we do the best we can to make people happy, whether it's the Pro version, or the free version.

Look for 1.9.19 soon.</description>
		<content:encoded><![CDATA[<p>This article is flat out false. We never intentionally crippled it, ever. We responded to your request, and you seem to be a little hasty. 1.9.18 was already prepped by the time we released it. </p>
<p>Please, relax. We&#8217;re not obligated nor required to do anything for what we freely have offered to everyone. WPtouch has been downloaded over 1,000,000 times. We have a lot of support requests related to it, and we do the best we can to make people happy, whether it&#8217;s the Pro version, or the free version.</p>
<p>Look for 1.9.19 soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: codestyling</title>
		<link>http://www.code-styling.de/english/wptouch-iphone-theme-and-the-crippled-translation#comment-1541</link>
		<dc:creator>codestyling</dc:creator>
		<pubDate>Sat, 28 Aug 2010 15:32:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.code-styling.de/?p=1383#comment-1541</guid>
		<description>I've already a slightly modified version of the GPL'ed repository plugin, but currently not running here.
It's planned for new upcomming design or new domains in near future. But forking this plugin results in many support requests I can't handle at the moment.
If my spare time will allow this in future, this fork will be done but for now it's on my todo list. And it's not as easy as expected because it seems, that WPtouch is a trademark, so this has to be checked first.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve already a slightly modified version of the GPL&#8217;ed repository plugin, but currently not running here.<br />
It&#8217;s planned for new upcomming design or new domains in near future. But forking this plugin results in many support requests I can&#8217;t handle at the moment.<br />
If my spare time will allow this in future, this fork will be done but for now it&#8217;s on my todo list. And it&#8217;s not as easy as expected because it seems, that WPtouch is a trademark, so this has to be checked first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.code-styling.de/english/wptouch-iphone-theme-and-the-crippled-translation#comment-1536</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Sat, 28 Aug 2010 11:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.code-styling.de/?p=1383#comment-1536</guid>
		<description>You should fork the plugin, if they don't include your patch anytime soon.</description>
		<content:encoded><![CDATA[<p>You should fork the plugin, if they don&#8217;t include your patch anytime soon.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

