<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Ruby on Rails and Web sites that won&#8217;t work on the T-Mobile Sidekick</title>
	<atom:link href="http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/</link>
	<description>A posting every day; an interesting idea every three months...</description>
	<lastBuildDate>Fri, 04 Dec 2009 15:40:58 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Behan</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-30917</link>
		<dc:creator>Michael Behan</dc:creator>
		<pubDate>Thu, 23 Aug 2007 06:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-30917</guid>
		<description>Check out the WURFL project:

http://wurfl.sourceforge.net/</description>
		<content:encoded><![CDATA[<p>Check out the WURFL project:</p>
<p><a href="http://wurfl.sourceforge.net/" rel="nofollow">http://wurfl.sourceforge.net/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cctvpro</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-18266</link>
		<dc:creator>cctvpro</dc:creator>
		<pubDate>Wed, 29 Nov 2006 11:46:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-18266</guid>
		<description>I share in your frustration.  I hope that the new .modi domain names address the issue.  I have to hope that companies that are smart enough to register these domains are smart enough to only use lighter more compatible technology when implementing the sites.</description>
		<content:encoded><![CDATA[<p>I share in your frustration.  I hope that the new .modi domain names address the issue.  I have to hope that companies that are smart enough to register these domains are smart enough to only use lighter more compatible technology when implementing the sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randall</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-18220</link>
		<dc:creator>Randall</dc:creator>
		<pubDate>Tue, 28 Nov 2006 21:05:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-18220</guid>
		<description>According to Firefox Quick Find, the words &quot;degrade gracefully&quot; haven&#039;t shown up in the thread, so here goes: degrade gracefully.

There are plenty of ways to use JavaScript without requiring it -- for instance, your &quot;edit item&quot; link can being up a page with an edit form in old browsers, and generate the form inline on new ones.  There are economic incentives against coding and testing that functionality -- the real solution is to bake graceful degradation into your frameworks; the same code that builds an inline form with JavaScript can spit out the same form as a standalone page from the server.  Perhaps if you do the hard work of building the framework now, you, yes you, will be the new hottness when downlevel mobile browsers get more popular.  (Or perhaps mobile browsers will skip a couple grades and go straight to being webapp-capable!)</description>
		<content:encoded><![CDATA[<p>According to Firefox Quick Find, the words &#8220;degrade gracefully&#8221; haven&#8217;t shown up in the thread, so here goes: degrade gracefully.</p>
<p>There are plenty of ways to use JavaScript without requiring it &#8212; for instance, your &#8220;edit item&#8221; link can being up a page with an edit form in old browsers, and generate the form inline on new ones.  There are economic incentives against coding and testing that functionality &#8212; the real solution is to bake graceful degradation into your frameworks; the same code that builds an inline form with JavaScript can spit out the same form as a standalone page from the server.  Perhaps if you do the hard work of building the framework now, you, yes you, will be the new hottness when downlevel mobile browsers get more popular.  (Or perhaps mobile browsers will skip a couple grades and go straight to being webapp-capable!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brian cantoni</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-18043</link>
		<dc:creator>brian cantoni</dc:creator>
		<pubDate>Mon, 20 Nov 2006 18:41:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-18043</guid>
		<description>I&#039;m maintaining a list of mobile-friendly websites here:
http://www.cantoni.org/palm/

I&#039;m finding that purpose-built mobile sites are the best. Rather than creating a mobile version of an entire site, create one that provides *just* the info useful to a mobile person.</description>
		<content:encoded><![CDATA[<p>I&#8217;m maintaining a list of mobile-friendly websites here:<br />
<a href="http://www.cantoni.org/palm/" rel="nofollow">http://www.cantoni.org/palm/</a></p>
<p>I&#8217;m finding that purpose-built mobile sites are the best. Rather than creating a mobile version of an entire site, create one that provides *just* the info useful to a mobile person.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gman</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-17989</link>
		<dc:creator>gman</dc:creator>
		<pubDate>Mon, 20 Nov 2006 07:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-17989</guid>
		<description>Mobile phones improve every year. By the time you got your entire web2.0 site dumbed down so it works on a mobile phone the phones would have progressed to the point you didn&#039;t need to in the first place.</description>
		<content:encoded><![CDATA[<p>Mobile phones improve every year. By the time you got your entire web2.0 site dumbed down so it works on a mobile phone the phones would have progressed to the point you didn&#8217;t need to in the first place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Molin</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-17893</link>
		<dc:creator>Michael Molin</dc:creator>
		<pubDate>Sat, 18 Nov 2006 03:51:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-17893</guid>
		<description>It&#039;s just the main reason for developing Mobile 2.0. My suggestion is to use a two-display solution as a standard hardware platform and divide the core content of a Web site for the better presentation on the main display and its framework - menu and the ads - for navigating on the second display-keyboard and easily access to the banner advertisements for consumers.

Cell Computer Project

http://geocities.com/gene_technics

Regards,</description>
		<content:encoded><![CDATA[<p>It&#8217;s just the main reason for developing Mobile 2.0. My suggestion is to use a two-display solution as a standard hardware platform and divide the core content of a Web site for the better presentation on the main display and its framework &#8211; menu and the ads &#8211; for navigating on the second display-keyboard and easily access to the banner advertisements for consumers.</p>
<p>Cell Computer Project</p>
<p><a href="http://geocities.com/gene_technics" rel="nofollow">http://geocities.com/gene_technics</a></p>
<p>Regards,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-17882</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Sat, 18 Nov 2006 00:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-17882</guid>
		<description>I&#039;m not up on the capabilities of modern web browsing phones but..you mentioned that one of them had XP under the hood....

Is there a Windows remote desktop client available for the phone you&#039;re now using?
I do nearly all my out-of office work and browsing via remote desktop these days....why maintain several desktops, favorites, settings files, purchase apps, etc, when you can have your desktop with you anywhere in the world?
  (just don&#039;t stream video :)</description>
		<content:encoded><![CDATA[<p>I&#8217;m not up on the capabilities of modern web browsing phones but..you mentioned that one of them had XP under the hood&#8230;.</p>
<p>Is there a Windows remote desktop client available for the phone you&#8217;re now using?<br />
I do nearly all my out-of office work and browsing via remote desktop these days&#8230;.why maintain several desktops, favorites, settings files, purchase apps, etc, when you can have your desktop with you anywhere in the world?<br />
  (just don&#8217;t stream video <img src='http://blogs.law.harvard.edu/philg/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 1gor</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-17876</link>
		<dc:creator>1gor</dc:creator>
		<pubDate>Fri, 17 Nov 2006 22:33:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-17876</guid>
		<description>I seem to remember how I couldn&#039;t get into ACS-based website in 1999  because my browser could not save cookies. Websites with ugly browser-based login windows (apache .htaccess etc.) were OK.

Was ACS also a sort of &quot;grand tool&quot; of its time?</description>
		<content:encoded><![CDATA[<p>I seem to remember how I couldn&#8217;t get into ACS-based website in 1999  because my browser could not save cookies. Websites with ugly browser-based login windows (apache .htaccess etc.) were OK.</p>
<p>Was ACS also a sort of &#8220;grand tool&#8221; of its time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tristan</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-17870</link>
		<dc:creator>Tristan</dc:creator>
		<pubDate>Fri, 17 Nov 2006 21:26:31 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-17870</guid>
		<description>The fact that the Sidekick can multi task so well means that even if a website is loading slowly, you can be doing email, chatting on IM, checking your Calender, writing a text message all while it loads in the background. 

Congrats on getting a good device. The keykboard on the Sidekick 3 is the most usable of any PDA I&#039;ve ever tried, and multi tasking on the Sidekick 3 simply rocks. I even tried a Blackberry previously and it was not as good.  

You might want to check out 

http://www.hiptop.com/forums 

which is the online community for all things Sidekick.</description>
		<content:encoded><![CDATA[<p>The fact that the Sidekick can multi task so well means that even if a website is loading slowly, you can be doing email, chatting on IM, checking your Calender, writing a text message all while it loads in the background. </p>
<p>Congrats on getting a good device. The keykboard on the Sidekick 3 is the most usable of any PDA I&#8217;ve ever tried, and multi tasking on the Sidekick 3 simply rocks. I even tried a Blackberry previously and it was not as good.  </p>
<p>You might want to check out </p>
<p><a href="http://www.hiptop.com/forums" rel="nofollow">http://www.hiptop.com/forums</a> </p>
<p>which is the online community for all things Sidekick.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-work-on-the-t-mobile-sidekick/comment-page-1/#comment-17803</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 16 Nov 2006 17:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/philg/2006/11/15/ruby-on-rails-and-web-sites-that-wont-w#comment-17803</guid>
		<description>I use my Treo a lot for mobile web browsing, which I would imagine is similar in capabilities to the Sidekick. Web developers do need to realise that more and more mobile devices will be being used. So many sites are so bloated these days, it&#039;s not even funny...

Some great mobile websites :

http://news.bbc.co.uk/text_only.stm
http://mobile.wunderground.com/
http://www.otweb.com/pda.html
http://www.google.com/pda (Regular www.google.com is also good).</description>
		<content:encoded><![CDATA[<p>I use my Treo a lot for mobile web browsing, which I would imagine is similar in capabilities to the Sidekick. Web developers do need to realise that more and more mobile devices will be being used. So many sites are so bloated these days, it&#8217;s not even funny&#8230;</p>
<p>Some great mobile websites :</p>
<p><a href="http://news.bbc.co.uk/text_only.stm" rel="nofollow">http://news.bbc.co.uk/text_only.stm</a><br />
<a href="http://mobile.wunderground.com/" rel="nofollow">http://mobile.wunderground.com/</a><br />
<a href="http://www.otweb.com/pda.html" rel="nofollow">http://www.otweb.com/pda.html</a><br />
<a href="http://www.google.com/pda" rel="nofollow">http://www.google.com/pda</a> (Regular <a href="http://www.google.com" rel="nofollow">http://www.google.com</a> is also good).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
