<?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: Two tips for iPhone developers</title>
	<atom:link href="http://www.brucelawson.co.uk/2009/two-tips-for-iphone-developers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brucelawson.co.uk/2009/two-tips-for-iphone-developers/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 14:14:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: M1chel</title>
		<link>http://www.brucelawson.co.uk/2009/two-tips-for-iphone-developers/comment-page-1/#comment-622401</link>
		<dc:creator>M1chel</dc:creator>
		<pubDate>Mon, 03 Aug 2009 10:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=1798#comment-622401</guid>
		<description>sorry for the double post but I think I might be helping:

on the page that ask the capthca there&#039;s this error showing
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/brucelaw/public_html/wp-content/plugins/SK2/sk2_second_chance.php:2) in /home/brucelaw/public_html/wp-content/plugins/easy-contact/econtact.php on line 112


Also, I would recommend to use something to make the page redirects you back to blog after the captcha is accepted or at least place a link, coz now it&#039;s a landing page. which is a bit of a usability nightmare.
Hope I helped. 
bye</description>
		<content:encoded><![CDATA[<p>sorry for the double post but I think I might be helping:</p>
<p>on the page that ask the capthca there&#8217;s this error showing<br />
Warning: session_start() [function.session-start]: Cannot send session cache limiter &#8211; headers already sent (output started at /home/brucelaw/public_html/wp-content/plugins/SK2/sk2_second_chance.php:2) in /home/brucelaw/public_html/wp-content/plugins/easy-contact/econtact.php on line 112</p>
<p>Also, I would recommend to use something to make the page redirects you back to blog after the captcha is accepted or at least place a link, coz now it&#8217;s a landing page. which is a bit of a usability nightmare.<br />
Hope I helped.<br />
bye</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M1chel</title>
		<link>http://www.brucelawson.co.uk/2009/two-tips-for-iphone-developers/comment-page-1/#comment-622400</link>
		<dc:creator>M1chel</dc:creator>
		<pubDate>Mon, 03 Aug 2009 10:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=1798#comment-622400</guid>
		<description>ahahahaahah 
I was reading the tutorial by Paolo Ranoso on nettuts which you commented and I followed your link here thinking at another in depth tutorial, instead I found quite a piece of advice.

I agree with you, but I&#039;m also laughing a lot coz I was expecting a bulleted list tutorial and I got an angry man :D

Thanks for the advice and great blog. I loved your accessibility guidelines for wordpress on another article.</description>
		<content:encoded><![CDATA[<p>ahahahaahah<br />
I was reading the tutorial by Paolo Ranoso on nettuts which you commented and I followed your link here thinking at another in depth tutorial, instead I found quite a piece of advice.</p>
<p>I agree with you, but I&#8217;m also laughing a lot coz I was expecting a bulleted list tutorial and I got an angry man <img src='http://www.brucelawson.co.uk/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
<p>Thanks for the advice and great blog. I loved your accessibility guidelines for wordpress on another article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zeke Franco</title>
		<link>http://www.brucelawson.co.uk/2009/two-tips-for-iphone-developers/comment-page-1/#comment-617377</link>
		<dc:creator>Zeke Franco</dc:creator>
		<pubDate>Mon, 06 Jul 2009 08:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=1798#comment-617377</guid>
		<description>My comment had some of the code strip out. :( You can view the full comment here: http://zeke.franco.name/items/view/4243</description>
		<content:encoded><![CDATA[<p>My comment had some of the code strip out. <img src='http://www.brucelawson.co.uk/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />  You can view the full comment here: <a href="http://zeke.franco.name/items/view/4243" rel="nofollow">http://zeke.franco.name/items/view/4243</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zeke Franco</title>
		<link>http://www.brucelawson.co.uk/2009/two-tips-for-iphone-developers/comment-page-1/#comment-617372</link>
		<dc:creator>Zeke Franco</dc:creator>
		<pubDate>Mon, 06 Jul 2009 07:54:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=1798#comment-617372</guid>
		<description>You don&#039;t have to do sniffing you can create separate styles and deliver it like this.

@media only screen and (max-device-width: 480px) {
  selector {
    property:value;
  }
}

or via a separate style sheet like this

&lt;!--[if !IE]&gt;--&gt;

&lt;!--

By using specific style sheets you are just enhancing the experience for a subset of users. Which is a good thing. If the user&#039;s browser doesn&#039;t understand the the special style sheet the will just get the regular (or mobile) style sheet.

The same thing can be down with javascript you can enhance the content based on the user&#039;s device. You just need to make sure the JavaScript your using is supported by running some tests.

I don&#039;t hear people complaining about how some Web sites deliver CSS3 and HTML5 to browsers that can understand it. For example IE7 won&#039;t get text-shadow but Safari users will. Content is still there it&#039;s just you&#039;ve added some nice details for people who have a progressive browser.</description>
		<content:encoded><![CDATA[<p>You don&#8217;t have to do sniffing you can create separate styles and deliver it like this.</p>
<p>@media only screen and (max-device-width: 480px) {<br />
  selector {<br />
    property:value;<br />
  }<br />
}</p>
<p>or via a separate style sheet like this</p>
<p><!--[if !IE]&gt;--></p>
<p>&lt;!&#8211;</p>
<p>By using specific style sheets you are just enhancing the experience for a subset of users. Which is a good thing. If the user&#8217;s browser doesn&#8217;t understand the the special style sheet the will just get the regular (or mobile) style sheet.</p>
<p>The same thing can be down with javascript you can enhance the content based on the user&#8217;s device. You just need to make sure the JavaScript your using is supported by running some tests.</p>
<p>I don&#8217;t hear people complaining about how some Web sites deliver CSS3 and HTML5 to browsers that can understand it. For example IE7 won&#8217;t get text-shadow but Safari users will. Content is still there it&#8217;s just you&#8217;ve added some nice details for people who have a progressive browser.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Ramsden</title>
		<link>http://www.brucelawson.co.uk/2009/two-tips-for-iphone-developers/comment-page-1/#comment-617137</link>
		<dc:creator>Andrew Ramsden</dc:creator>
		<pubDate>Fri, 03 Jul 2009 22:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=1798#comment-617137</guid>
		<description>Very true Bruce, this sort of technique should be used with care.

Most sites are ok to use on iPhone. But there is sometimes a need for &quot;mobile&quot; layouts. For example, sites with full page line width are tricky (because on iPhone you can&#039;t control the width of your browser &quot;window&quot; so to speak). To make those sites readable means to zoom in and use horizontal scrolling back and forwards for every line. Yuck!

Wikipedia is a good example of this problem, which us why I appreciate the mobile version of their site.

This is a good approach for Wikipedia because they have a well known site design/layout and a large existing user base, so changing their main site layout may not be a viable option (at least without much testing).</description>
		<content:encoded><![CDATA[<p>Very true Bruce, this sort of technique should be used with care.</p>
<p>Most sites are ok to use on iPhone. But there is sometimes a need for &#8220;mobile&#8221; layouts. For example, sites with full page line width are tricky (because on iPhone you can&#8217;t control the width of your browser &#8220;window&#8221; so to speak). To make those sites readable means to zoom in and use horizontal scrolling back and forwards for every line. Yuck!</p>
<p>Wikipedia is a good example of this problem, which us why I appreciate the mobile version of their site.</p>
<p>This is a good approach for Wikipedia because they have a well known site design/layout and a large existing user base, so changing their main site layout may not be a viable option (at least without much testing).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amadeus</title>
		<link>http://www.brucelawson.co.uk/2009/two-tips-for-iphone-developers/comment-page-1/#comment-617136</link>
		<dc:creator>Amadeus</dc:creator>
		<pubDate>Fri, 03 Jul 2009 22:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.brucelawson.co.uk/?p=1798#comment-617136</guid>
		<description>You&#039;re kidding right? Do you even understand iPhone web development? There&#039;s something called screen specific stylesheets which is perfect for optimizing the experience for an iPhone. Let&#039;s face it, zoom and dragging in 2 directions is a poor experience for a site designed to be taken in vertically. Furthermore, I have never seen a site lock in the zoom when they didn&#039;t have an iPhone/mobile specific stylesheets. News flash, it doesn&#039;t require &#039;browser sniffing&#039;. It seems you are creating so called &#039;tips&#039; to give yourself credibility when in reality it&#039;s common sense.

I don&#039;t mean to be rude, but posts like this make me despise most &#039;blogs&#039;.

Seems I need to stop following the Twitter Boaglinks account.</description>
		<content:encoded><![CDATA[<p>You&#8217;re kidding right? Do you even understand iPhone web development? There&#8217;s something called screen specific stylesheets which is perfect for optimizing the experience for an iPhone. Let&#8217;s face it, zoom and dragging in 2 directions is a poor experience for a site designed to be taken in vertically. Furthermore, I have never seen a site lock in the zoom when they didn&#8217;t have an iPhone/mobile specific stylesheets. News flash, it doesn&#8217;t require &#8216;browser sniffing&#8217;. It seems you are creating so called &#8216;tips&#8217; to give yourself credibility when in reality it&#8217;s common sense.</p>
<p>I don&#8217;t mean to be rude, but posts like this make me despise most &#8216;blogs&#8217;.</p>
<p>Seems I need to stop following the Twitter Boaglinks account.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

