<?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: W3C Widgets 1.0 Requirements</title>
	<atom:link href="http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/</link>
	<description>All Widgets, All the Time, News, Reviews, Previews, Articles and Interviews</description>
	<lastBuildDate>Tue, 09 Mar 2010 01:27:15 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: New W3C Widgets 1.0 Drafts &#124; Widgets Lab</title>
		<link>http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/comment-page-1/#comment-340685</link>
		<dc:creator>New W3C Widgets 1.0 Drafts &#124; Widgets Lab</dc:creator>
		<pubDate>Wed, 30 Apr 2008 04:08:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/#comment-340685</guid>
		<description>[...] in the road for a final Widgets 1.0 Document, over a year from first intentions and 9 months since i first reported about this when i was starting my stint here at [...]</description>
		<content:encoded><![CDATA[<p>[...] in the road for a final Widgets 1.0 Document, over a year from first intentions and 9 months since i first reported about this when i was starting my stint here at [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Avatar</title>
		<link>http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/comment-page-1/#comment-77282</link>
		<dc:creator>Avatar</dc:creator>
		<pubDate>Wed, 18 Jul 2007 06:21:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/#comment-77282</guid>
		<description>I think you have understood correctly what i meant, and you have put into more technical terms, but i think it still can be done, the only question is the how to justificate putting it as a standard, and in what measure of course.

Abut the e-mails, sure, i will follow your blog and will think in how to expose things better and also thing of more specific case of use you can work with.</description>
		<content:encoded><![CDATA[<p>I think you have understood correctly what i meant, and you have put into more technical terms, but i think it still can be done, the only question is the how to justificate putting it as a standard, and in what measure of course.</p>
<p>Abut the e-mails, sure, i will follow your blog and will think in how to expose things better and also thing of more specific case of use you can work with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcos Caceres</title>
		<link>http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/comment-page-1/#comment-76397</link>
		<dc:creator>Marcos Caceres</dc:creator>
		<pubDate>Sat, 14 Jul 2007 01:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/#comment-76397</guid>
		<description>I&#039;m sorry Avatar, I&#039;m still not fully understanding what you mean:( However, what you are hinting at is interesting and I would really like to hear more. Once you write up some use cases please email me so we can continue to discuss this. 

From what I understand from above you are asking for (1) a widget render context (window) to be able to dynamically grow its width and height? And (2) some kind of base color palette? 

In case I&#039;ve understood 1 correctly, this should already be allowed by the spec. In the case of 2, every device displays color differently and I&#039;m not sure that having a color palette would be much help to creating widgets that blend well with their surroundings.  

Mobile phone screens are able to display more and more colors every year (eg. the iPhone)
For example, most modern phones can reproduce 65,000, LG&#039;s Prada can do 256,000 colors, and Nokia&#039;s N95 can reproduce 16.7 million colors, i think. The DPI of screens is also rapidly increasing (eg. iPhone&#039;s 160 dpi), which poses further problems for developers. The w3c has quite a few activities looking at how to overcome these problems, particularly the the Ubiquitous and Mobile Web initiatives and the Device Independence Working Group and CSS Working Group.  
  
Also, color theory states that colors appear as they do because of the colors they have next to them. So people could mix whatever palette you give them and still create a design that does not work well (especially if you can control what color sits next to the widget). 

Regarding time frame: the iPhone brought a bit of seismic shift to mobile widgets, and so has the rapid emergence of the mobile widgets market over the last 6 months. We are investigating the mobility issues right now. However, we hope to have this all wrapped up by sometime in between 2008-2009.</description>
		<content:encoded><![CDATA[<p>I&#8217;m sorry Avatar, I&#8217;m still not fully understanding what you mean:( However, what you are hinting at is interesting and I would really like to hear more. Once you write up some use cases please email me so we can continue to discuss this. </p>
<p>From what I understand from above you are asking for (1) a widget render context (window) to be able to dynamically grow its width and height? And (2) some kind of base color palette? </p>
<p>In case I&#8217;ve understood 1 correctly, this should already be allowed by the spec. In the case of 2, every device displays color differently and I&#8217;m not sure that having a color palette would be much help to creating widgets that blend well with their surroundings.  </p>
<p>Mobile phone screens are able to display more and more colors every year (eg. the iPhone)<br />
For example, most modern phones can reproduce 65,000, LG&#8217;s Prada can do 256,000 colors, and Nokia&#8217;s N95 can reproduce 16.7 million colors, i think. The DPI of screens is also rapidly increasing (eg. iPhone&#8217;s 160 dpi), which poses further problems for developers. The w3c has quite a few activities looking at how to overcome these problems, particularly the the Ubiquitous and Mobile Web initiatives and the Device Independence Working Group and CSS Working Group.  </p>
<p>Also, color theory states that colors appear as they do because of the colors they have next to them. So people could mix whatever palette you give them and still create a design that does not work well (especially if you can control what color sits next to the widget). </p>
<p>Regarding time frame: the iPhone brought a bit of seismic shift to mobile widgets, and so has the rapid emergence of the mobile widgets market over the last 6 months. We are investigating the mobility issues right now. However, we hope to have this all wrapped up by sometime in between 2008-2009.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Strategy by Jeremiah &#187; Widgets, a viable Web Marketing Strategy</title>
		<link>http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/comment-page-1/#comment-75920</link>
		<dc:creator>Web Strategy by Jeremiah &#187; Widgets, a viable Web Marketing Strategy</dc:creator>
		<pubDate>Thu, 12 Jul 2007 02:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/#comment-75920</guid>
		<description>[...] There&#8217;s an interesting program by the W3C to standardize widgets. Makes sense. [...]</description>
		<content:encoded><![CDATA[<p>[...] There&#8217;s an interesting program by the W3C to standardize widgets. Makes sense. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: StickiWidgets &#187; Blog Archive &#187; W3C Widgets 1.0 Requirements Updated</title>
		<link>http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/comment-page-1/#comment-75794</link>
		<dc:creator>StickiWidgets &#187; Blog Archive &#187; W3C Widgets 1.0 Requirements Updated</dc:creator>
		<pubDate>Wed, 11 Jul 2007 15:34:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.widgetslab.com/2007/07/10/w3c-widgets-10-requirements/#comment-75794</guid>
		<description>[...] The World Wide Web Consortium (W3C) updated the Widgets 1.0 Requirements document a few days ago. The document is a good read and widgets standardizations would be a nice move. We like the direction this is going and in particular we like what Marcos Caceres (editor of the requirements spec) had to say in a comment posted over at Widgets Lab. &#8220;I donâ€™t think it should be the w3câ€™s place to tell designers or widget vendors what widgets should look like, but, instead, instead, the w3c should specify the tools developers need to create awesome looking/functioning widgets.&#8221; - Marcos Caceres [...]</description>
		<content:encoded><![CDATA[<p>[...] The World Wide Web Consortium (W3C) updated the Widgets 1.0 Requirements document a few days ago. The document is a good read and widgets standardizations would be a nice move. We like the direction this is going and in particular we like what Marcos Caceres (editor of the requirements spec) had to say in a comment posted over at Widgets Lab. &#8220;I donâ€™t think it should be the w3câ€™s place to tell designers or widget vendors what widgets should look like, but, instead, instead, the w3c should specify the tools developers need to create awesome looking/functioning widgets.&#8221; &#8211; Marcos Caceres [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.429 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-03-15 07:06:14 -->
