<?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"
	>
<channel>
	<title>Comments on: Ask your questions to the people behind Opera Widgets on mobile phones</title>
	<atom:link href="http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html/feed" rel="self" type="application/rss+xml" />
	<link>http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html</link>
	<description>A blog covering the latest buzz on the Opera browser and its competition.</description>
	<pubDate>Mon, 01 Dec 2008 16:22:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Daniel Goldman</title>
		<link>http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-61135</link>
		<dc:creator>Daniel Goldman</dc:creator>
		<pubDate>Fri, 11 May 2007 14:26:07 +0000</pubDate>
		<guid isPermaLink="false">http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-61135</guid>
		<description>comnut, the answers will come shortly.</description>
		<content:encoded><![CDATA[<p>comnut, the answers will come shortly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: comnut</title>
		<link>http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-61012</link>
		<dc:creator>comnut</dc:creator>
		<pubDate>Fri, 11 May 2007 07:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-61012</guid>
		<description>so is anyone going to answer these questions???

- or is it 'just an old blog', its dead, move along........

OH well, at least Firefox for Mobiles will be much better....</description>
		<content:encoded><![CDATA[<p>so is anyone going to answer these questions???</p>
<p>- or is it &#8216;just an old blog&#8217;, its dead, move along&#8230;&#8230;..</p>
<p>OH well, at least Firefox for Mobiles will be much better&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EC</title>
		<link>http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58357</link>
		<dc:creator>EC</dc:creator>
		<pubDate>Thu, 03 May 2007 17:12:30 +0000</pubDate>
		<guid isPermaLink="false">http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58357</guid>
		<description>Like Rocco asked in #2 above, what internal phone information can be accessed via these widgets? Is there some sort of API for this? 


ie can I access the Tools and Settings - not necessarily &lt;i&gt;change&lt;/i&gt; the settings, but at least view them, read-only... ;)</description>
		<content:encoded><![CDATA[<p>Like Rocco asked in #2 above, what internal phone information can be accessed via these widgets? Is there some sort of API for this? </p>
<p>ie can I access the Tools and Settings - not necessarily <i>change</i> the settings, but at least view them, read-only&#8230; <img src='http://operawatch.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johnnysaucepn</title>
		<link>http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58250</link>
		<dc:creator>johnnysaucepn</dc:creator>
		<pubDate>Thu, 03 May 2007 08:53:08 +0000</pubDate>
		<guid isPermaLink="false">http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58250</guid>
		<description>I guess a follow-up question would be: are there plans to make the documentation for writing mobile widgets available well in advance of the release, so we can get a head start?</description>
		<content:encoded><![CDATA[<p>I guess a follow-up question would be: are there plans to make the documentation for writing mobile widgets available well in advance of the release, so we can get a head start?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johnnysaucepn</title>
		<link>http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58243</link>
		<dc:creator>johnnysaucepn</dc:creator>
		<pubDate>Thu, 03 May 2007 08:38:25 +0000</pubDate>
		<guid isPermaLink="false">http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58243</guid>
		<description>Can we make widgets compatible across mobile and desktop? In other words, can I apply a handheld stylesheet to my desktop widget and expect it to work in Mobile, or will it have to be rewritten?</description>
		<content:encoded><![CDATA[<p>Can we make widgets compatible across mobile and desktop? In other words, can I apply a handheld stylesheet to my desktop widget and expect it to work in Mobile, or will it have to be rewritten?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rocco</title>
		<link>http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58231</link>
		<dc:creator>Rocco</dc:creator>
		<pubDate>Thu, 03 May 2007 07:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58231</guid>
		<description>Hi, I'm really looking forward to this and feel it's a great opportunity for developers. Here's a couple of questions:

1. How are Opera desktop widgets different from the ones you can put on your phone? i mean except the obvious differences in screen size, would it be possible to just use the desktop version of a widget and put it on a phone?

2. Which device APIs are accessible to a widget on my phone? can i e.g. get info about the CPU usage or remaining battery power?

3. How do you put these widgets on your phone? can you download them through the browser and/or install them directly using a data cable or Bluetooth?

Thanks!</description>
		<content:encoded><![CDATA[<p>Hi, I&#8217;m really looking forward to this and feel it&#8217;s a great opportunity for developers. Here&#8217;s a couple of questions:</p>
<p>1. How are Opera desktop widgets different from the ones you can put on your phone? i mean except the obvious differences in screen size, would it be possible to just use the desktop version of a widget and put it on a phone?</p>
<p>2. Which device APIs are accessible to a widget on my phone? can i e.g. get info about the CPU usage or remaining battery power?</p>
<p>3. How do you put these widgets on your phone? can you download them through the browser and/or install them directly using a data cable or Bluetooth?</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kyleabaker</title>
		<link>http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58202</link>
		<dc:creator>kyleabaker</dc:creator>
		<pubDate>Thu, 03 May 2007 05:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://operawatch.com/news/2007/05/ask-your-questions-to-the-people-behind-opera-widgets-on-mobile-phones.html#comment-58202</guid>
		<description>Is there any way that we can test our widgets in Opera on a desktop to see how they will appear on a mobile? We cannot really test widgets with xmlhttp requests so I'm just hoping there is another way to go about this. I don't have a phone to test with either, haha.</description>
		<content:encoded><![CDATA[<p>Is there any way that we can test our widgets in Opera on a desktop to see how they will appear on a mobile? We cannot really test widgets with xmlhttp requests so I&#8217;m just hoping there is another way to go about this. I don&#8217;t have a phone to test with either, haha.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
