<?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: Iris Browser 1.1.0</title>
	<atom:link href="http://www.mobilitysite.com/2009/02/iris-browser-110/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mobilitysite.com/2009/02/iris-browser-110/</link>
	<description>Mobile News, Reviews, and Views.</description>
	<lastBuildDate>Tue, 24 Nov 2009 03:10:04 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Pony99CA</title>
		<link>http://www.mobilitysite.com/2009/02/iris-browser-110/comment-page-1/#comment-15575</link>
		<dc:creator>Pony99CA</dc:creator>
		<pubDate>Tue, 24 Feb 2009 21:31:15 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/02/iris-browser-110/#comment-15575</guid>
		<description>@Jack &amp; doogald:

Thanks for the info about running Iris on the Q9m.  I may try it out.

@doogald:
&lt;blockquote&gt;I haven’t tried it with my Q9m yet, but the download page does clearly say, “The browser has been tested on a variety of Windows Mobile 5 and 6 devices, including Classic and Professional (Smartphone, PocketPC) editions[...]&quot;&lt;/blockquote&gt;
Yes, I read that, too, but I hardly think that it&#039;s clear.  As I&#039;m sure you know, WM Classic and Professional devices are both touchscreen devices (Pocket PCs and Pocket PC phones).  Putting &quot;Smartphone, Pocket PC&quot; in parentheses appears to be clarifying either what &quot;Classic and Professional&quot; or just &quot;Professional&quot; means.

Also, given that Microsoft started referring to both WM Standard and WM Professional devices as &quot;Smartphones&quot;, using &quot;Smartphone&quot; inside the parentheses could be inferred to mean the newer definition.

That&#039;s why I asked.  Trust me, I parse words &lt;b&gt;very&lt;/b&gt; carefully, and it would take a very liberal parsing to infer that sentence meant that non-touchscreen devices were supported.

I would have written it as follows:

&quot;The browser has been tested on a variety of Windows Mobile 5 and 6 devices, including WM Classic/Pocket PC, WM Professional/Pocket PC Phone and WM Standard/Smartphone editions.&quot;

I think that avoids any confusion about whether non-touchscreen devices are supported.

Steve</description>
		<content:encoded><![CDATA[<p>@Jack &amp; doogald:</p>
<p>Thanks for the info about running Iris on the Q9m.  I may try it out.</p>
<p>@doogald:</p>
<blockquote><p>I haven’t tried it with my Q9m yet, but the download page does clearly say, “The browser has been tested on a variety of Windows Mobile 5 and 6 devices, including Classic and Professional (Smartphone, PocketPC) editions[...]&#8220;</p></blockquote>
<p>Yes, I read that, too, but I hardly think that it&#8217;s clear.  As I&#8217;m sure you know, WM Classic and Professional devices are both touchscreen devices (Pocket PCs and Pocket PC phones).  Putting &#8220;Smartphone, Pocket PC&#8221; in parentheses appears to be clarifying either what &#8220;Classic and Professional&#8221; or just &#8220;Professional&#8221; means.</p>
<p>Also, given that Microsoft started referring to both WM Standard and WM Professional devices as &#8220;Smartphones&#8221;, using &#8220;Smartphone&#8221; inside the parentheses could be inferred to mean the newer definition.</p>
<p>That&#8217;s why I asked.  Trust me, I parse words <b>very</b> carefully, and it would take a very liberal parsing to infer that sentence meant that non-touchscreen devices were supported.</p>
<p>I would have written it as follows:</p>
<p>&#8220;The browser has been tested on a variety of Windows Mobile 5 and 6 devices, including WM Classic/Pocket PC, WM Professional/Pocket PC Phone and WM Standard/Smartphone editions.&#8221;</p>
<p>I think that avoids any confusion about whether non-touchscreen devices are supported.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Cook</title>
		<link>http://www.mobilitysite.com/2009/02/iris-browser-110/comment-page-1/#comment-15567</link>
		<dc:creator>Jack Cook</dc:creator>
		<pubDate>Tue, 24 Feb 2009 05:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/02/iris-browser-110/#comment-15567</guid>
		<description>@ Steve

Yes I did install it on my Q9m Steve.  It was a fast and easy install.  I just used it for a short piece of time today browsing Google Reader reading my feeds.  I was pleased.  I will try it in the next day or so on my Touch Pro where I expect it will be very good.

On the Q9m, I did expereience memory issues with pages that have a lot of pictures. It did not load the default mobile page on some and that was disappointing (and yet it did on Google Reader).  For me, all the pages I want to visit are under My Google Reader and that works exactly as I would expect and want.

Overall, it works well and I am looking forward to testing it out it on my Pocket PCs

  

My primary use with it will be</description>
		<content:encoded><![CDATA[<p>@ Steve</p>
<p>Yes I did install it on my Q9m Steve.  It was a fast and easy install.  I just used it for a short piece of time today browsing Google Reader reading my feeds.  I was pleased.  I will try it in the next day or so on my Touch Pro where I expect it will be very good.</p>
<p>On the Q9m, I did expereience memory issues with pages that have a lot of pictures. It did not load the default mobile page on some and that was disappointing (and yet it did on Google Reader).  For me, all the pages I want to visit are under My Google Reader and that works exactly as I would expect and want.</p>
<p>Overall, it works well and I am looking forward to testing it out it on my Pocket PCs</p>
<p>My primary use with it will be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FClifton</title>
		<link>http://www.mobilitysite.com/2009/02/iris-browser-110/comment-page-1/#comment-15566</link>
		<dc:creator>FClifton</dc:creator>
		<pubDate>Tue, 24 Feb 2009 05:31:12 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/02/iris-browser-110/#comment-15566</guid>
		<description>Downloaded and tried on XV6800 running WM6.1.  Did not render images, and on the 3 websites I tried, when I attempted to log in, I got a screen saying the server couldn&#039;t be found.  Maybe a memory issue since XV6800 has only about 14M free.  Anyway, no go for me ;(</description>
		<content:encoded><![CDATA[<p>Downloaded and tried on XV6800 running WM6.1.  Did not render images, and on the 3 websites I tried, when I attempted to log in, I got a screen saying the server couldn&#8217;t be found.  Maybe a memory issue since XV6800 has only about 14M free.  Anyway, no go for me ;(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: doogald</title>
		<link>http://www.mobilitysite.com/2009/02/iris-browser-110/comment-page-1/#comment-15565</link>
		<dc:creator>doogald</dc:creator>
		<pubDate>Tue, 24 Feb 2009 03:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/02/iris-browser-110/#comment-15565</guid>
		<description>I&#039;ve used it for about 5 minutes on my Q9m; it works just fine. In fact, I really like this browser. It&#039;s fast, it doesn&#039;t seem to be using proxying (like Opera Mini, Skyfire, et. al.), and still gives accurate page rendering and quick page zooming. Nice.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve used it for about 5 minutes on my Q9m; it works just fine. In fact, I really like this browser. It&#8217;s fast, it doesn&#8217;t seem to be using proxying (like Opera Mini, Skyfire, et. al.), and still gives accurate page rendering and quick page zooming. Nice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: doogald</title>
		<link>http://www.mobilitysite.com/2009/02/iris-browser-110/comment-page-1/#comment-15558</link>
		<dc:creator>doogald</dc:creator>
		<pubDate>Tue, 24 Feb 2009 01:18:30 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/02/iris-browser-110/#comment-15558</guid>
		<description>I haven&#039;t tried it with my Q9m yet, but the download page does clearly say, &quot;The browser has been tested on a variety of Windows Mobile 5 and 6 devices, including Classic and Professional (Smartphone, PocketPC) editions, and we recommend 400MHz CPU and 128MB of RAM at this time, though it is known to work well on 200MHz processors and 64MB devices.&quot;

I&#039;ll probably try installing it tomorrow myself.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t tried it with my Q9m yet, but the download page does clearly say, &#8220;The browser has been tested on a variety of Windows Mobile 5 and 6 devices, including Classic and Professional (Smartphone, PocketPC) editions, and we recommend 400MHz CPU and 128MB of RAM at this time, though it is known to work well on 200MHz processors and 64MB devices.&#8221;</p>
<p>I&#8217;ll probably try installing it tomorrow myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pony99CA</title>
		<link>http://www.mobilitysite.com/2009/02/iris-browser-110/comment-page-1/#comment-15555</link>
		<dc:creator>Pony99CA</dc:creator>
		<pubDate>Mon, 23 Feb 2009 23:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/02/iris-browser-110/#comment-15555</guid>
		<description>@Jack:

Did you try this on your Motorola Q9m?  The download page isn&#039;t clear about whether it works with WM Standard/Smartphone non-touchscreen devices or not.

Steve</description>
		<content:encoded><![CDATA[<p>@Jack:</p>
<p>Did you try this on your Motorola Q9m?  The download page isn&#8217;t clear about whether it works with WM Standard/Smartphone non-touchscreen devices or not.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Coddington</title>
		<link>http://www.mobilitysite.com/2009/02/iris-browser-110/comment-page-1/#comment-15546</link>
		<dc:creator>Matt Coddington</dc:creator>
		<pubDate>Mon, 23 Feb 2009 19:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/02/iris-browser-110/#comment-15546</guid>
		<description>I went ahead and installed it - pretty impressive.  I have to admit, it&#039;s getting a little confusing remembering which browser does what!  Opera, Skyfire, Bolt, and now Iris - so many choices!

I still need to run this through it&#039;s paces to make a final determination, but it&#039;s certainly peppy!  No freezing up (yet)!

Matt</description>
		<content:encoded><![CDATA[<p>I went ahead and installed it &#8211; pretty impressive.  I have to admit, it&#8217;s getting a little confusing remembering which browser does what!  Opera, Skyfire, Bolt, and now Iris &#8211; so many choices!</p>
<p>I still need to run this through it&#8217;s paces to make a final determination, but it&#8217;s certainly peppy!  No freezing up (yet)!</p>
<p>Matt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Coddington</title>
		<link>http://www.mobilitysite.com/2009/02/iris-browser-110/comment-page-1/#comment-15544</link>
		<dc:creator>Matt Coddington</dc:creator>
		<pubDate>Mon, 23 Feb 2009 19:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://mobilitysite.com/2009/02/iris-browser-110/#comment-15544</guid>
		<description>Upon getting to the Download section of their site, I noticed a statement about Touch Diamond and Touch Pro devices freezing up.  They say a driver needs some work...  darn.  I have a Pro and wanted to check it out!</description>
		<content:encoded><![CDATA[<p>Upon getting to the Download section of their site, I noticed a statement about Touch Diamond and Touch Pro devices freezing up.  They say a driver needs some work&#8230;  darn.  I have a Pro and wanted to check it out!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
