<?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: Mobile Stylesheets</title>
	<atom:link href="http://povich.co.uk/blog/2009/01/mobile-stylesheets/feed/" rel="self" type="application/rss+xml" />
	<link>http://povich.co.uk/blog/2009/01/mobile-stylesheets/</link>
	<description>Ramblings of Jim Whiteside, and some good old Norfolk squit.</description>
	<pubDate>Thu, 09 Feb 2012 00:23:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mat</title>
		<link>http://povich.co.uk/blog/2009/01/mobile-stylesheets/comment-page-1/#comment-158</link>
		<dc:creator>mat</dc:creator>
		<pubDate>Wed, 07 Jan 2009 15:26:18 +0000</pubDate>
		<guid isPermaLink="false">http://povich.co.uk/blog/?p=173#comment-158</guid>
		<description>we run m.moblog.net for mobile devices.  people have to choose to go there (ie, we don't attempt detection on page load), but it's nice to be able to offer both full-fat and lightweight versions of the site - there's nothing to stop me using full-powered moblog on my phone if I want to zoom and pan and load lots of html and so on, and conversely, I can get a fast, light version of the site too.  It all depends on where I am and how fast my connection is (2G,3G,Wifi) and how much time I have to kill.

Django has a Thing for "mobilising" content, which is OK for simple stuff, but obviously it's better in the long run to just roll your own "mobile" output filters.  It's hardly rocket science, after all.  Especially seeing as, for moblog at least, we have multiple output filters already - html and xml views are already happening into most of our data, it's not that big a deal to add a stripped, lean-but-functional, m-html too.

mobile css is nice to work with though.  support is so much more consistent than for desktop browsers - no more dirty hacks just to make IE6 work!</description>
		<content:encoded><![CDATA[<p>we run m.moblog.net for mobile devices.  people have to choose to go there (ie, we don&#8217;t attempt detection on page load), but it&#8217;s nice to be able to offer both full-fat and lightweight versions of the site - there&#8217;s nothing to stop me using full-powered moblog on my phone if I want to zoom and pan and load lots of html and so on, and conversely, I can get a fast, light version of the site too.  It all depends on where I am and how fast my connection is (2G,3G,Wifi) and how much time I have to kill.</p>
<p>Django has a Thing for &#8220;mobilising&#8221; content, which is OK for simple stuff, but obviously it&#8217;s better in the long run to just roll your own &#8220;mobile&#8221; output filters.  It&#8217;s hardly rocket science, after all.  Especially seeing as, for moblog at least, we have multiple output filters already - html and xml views are already happening into most of our data, it&#8217;s not that big a deal to add a stripped, lean-but-functional, m-html too.</p>
<p>mobile css is nice to work with though.  support is so much more consistent than for desktop browsers - no more dirty hacks just to make IE6 work!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

