<?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: Copper: an experiment with CSS</title>
	<atom:link href="http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/</link>
	<description>"Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios."</description>
	<lastBuildDate>Sun, 26 Sep 2010 15:08:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: George Antoniadis</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1079</link>
		<dc:creator>George Antoniadis</dc:creator>
		<pubDate>Mon, 20 Jul 2009 08:06:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1079</guid>
		<description>Something interesting but possibly hard to make happen is the &quot;template layout&quot; of css3.

http://www.w3.org/TR/2009/WD-css3-layout-20090402/

Would be a very interesting way to create panels and stuff inside windows.</description>
		<content:encoded><![CDATA[<p>Something interesting but possibly hard to make happen is the &#8220;template layout&#8221; of css3.</p>
<p><a href="http://www.w3.org/TR/2009/WD-css3-layout-20090402/" rel="nofollow">http://www.w3.org/TR/2009/WD-css3-layout-20090402/</a></p>
<p>Would be a very interesting way to create panels and stuff inside windows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: More CSS thoughts - …for the adult in you</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1061</link>
		<dc:creator>More CSS thoughts - …for the adult in you</dc:creator>
		<pubDate>Sat, 18 Jul 2009 23:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1061</guid>
		<description>[...] The recent discussion about CSS themes looks as though it may become one of the most interesting new ideas in theming in recent years. Here are some further thoughts on what may evolve from this. [...]</description>
		<content:encoded><![CDATA[<p>[...] The recent discussion about CSS themes looks as though it may become one of the most interesting new ideas in theming in recent years. Here are some further thoughts on what may evolve from this. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexandre Mazari</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1057</link>
		<dc:creator>Alexandre Mazari</dc:creator>
		<pubDate>Thu, 16 Jul 2009 23:23:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1057</guid>
		<description>One (not so) crazy idea could be the use of WebKit&#039;s WebView as the drawing area. This way the theme could just be a standard HTML file with its CSS companion. And why not some JS for some graphical logic.
The benefits are numerous : standard, lots of authoring tools, very capable graphical system (ex : see css transformation/transition recent work) etc...

The challenge is to plumb such a ui to the GObject/native code. this could be achieved using Seed to expose the GObjects in the webview&#039;s javascript context or using the Webkit DOM bindings, exposing divs and stuff to the native word (see webkit bug #16401).
This approach could even be used for applications ui ala webos or chrome os :)</description>
		<content:encoded><![CDATA[<p>One (not so) crazy idea could be the use of WebKit&#8217;s WebView as the drawing area. This way the theme could just be a standard HTML file with its CSS companion. And why not some JS for some graphical logic.<br />
The benefits are numerous : standard, lots of authoring tools, very capable graphical system (ex : see css transformation/transition recent work) etc&#8230;</p>
<p>The challenge is to plumb such a ui to the GObject/native code. this could be achieved using Seed to expose the GObjects in the webview&#8217;s javascript context or using the Webkit DOM bindings, exposing divs and stuff to the native word (see webkit bug #16401).<br />
This approach could even be used for applications ui ala webos or chrome os :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Thurman</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1055</link>
		<dc:creator>Thomas Thurman</dc:creator>
		<pubDate>Thu, 16 Jul 2009 22:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1055</guid>
		<description>@Jorge:

You&#039;re entirely right: having explicit topleft, topright, etc., boxes was a mistake.  If I do more work on this I&#039;ll just have the frame element and allow you to set border-images on it to get the same results far more simply.</description>
		<content:encoded><![CDATA[<p>@Jorge:</p>
<p>You&#8217;re entirely right: having explicit topleft, topright, etc., boxes was a mistake.  If I do more work on this I&#8217;ll just have the frame element and allow you to set border-images on it to get the same results far more simply.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A meta-post about blogging &#171; ᛏᚦ</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1051</link>
		<dc:creator>A meta-post about blogging &#171; ᛏᚦ</dc:creator>
		<pubDate>Thu, 16 Jul 2009 22:17:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1051</guid>
		<description>[...] on on the Metacity blog, including the development of optional and experimental subsystems for CSS theming and window matching, and whether applications should be able to extend the window menu (so if you [...]</description>
		<content:encoded><![CDATA[<p>[...] on on the Metacity blog, including the development of optional and experimental subsystems for CSS theming and window matching, and whether applications should be able to extend the window menu (so if you [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jorge</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1041</link>
		<dc:creator>Jorge</dc:creator>
		<pubDate>Thu, 16 Jul 2009 07:35:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1041</guid>
		<description>I think the css format is a great idea.

Just some thoughts and suggestions:
- Consider the border-image rule [1] 
- And webkit gradients too [2] 
- I think it makes more sense edges as the padding or/and the border of the window instead being boxes by themselves, but this would be a little limiting.
- I agree with the others, border-radius is there, so I think is the same as the previous point, it is necessary that edges being represented as boxes?

[1] http://www.w3.org/TR/css3-background/#the-border-image
[2] http://webkit.org/blog/175/introducing-css-gradients/</description>
		<content:encoded><![CDATA[<p>I think the css format is a great idea.</p>
<p>Just some thoughts and suggestions:<br />
- Consider the border-image rule [1]<br />
- And webkit gradients too [2]<br />
- I think it makes more sense edges as the padding or/and the border of the window instead being boxes by themselves, but this would be a little limiting.<br />
- I agree with the others, border-radius is there, so I think is the same as the previous point, it is necessary that edges being represented as boxes?</p>
<p>[1] <a href="http://www.w3.org/TR/css3-background/#the-border-image" rel="nofollow">http://www.w3.org/TR/css3-background/#the-border-image</a><br />
[2] <a href="http://webkit.org/blog/175/introducing-css-gradients/" rel="nofollow">http://webkit.org/blog/175/introducing-css-gradients/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier Samyn</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1036</link>
		<dc:creator>Olivier Samyn</dc:creator>
		<pubDate>Wed, 15 Jul 2009 23:04:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1036</guid>
		<description>Just for reference, vendor keywords is formalized in CSS 2.1:
http://www.w3.org/TR/2009/CR-CSS2-20090423/syndata.html#vendor-keywords</description>
		<content:encoded><![CDATA[<p>Just for reference, vendor keywords is formalized in CSS 2.1:<br />
<a href="http://www.w3.org/TR/2009/CR-CSS2-20090423/syndata.html#vendor-keywords" rel="nofollow">http://www.w3.org/TR/2009/CR-CSS2-20090423/syndata.html#vendor-keywords</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: person</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1034</link>
		<dc:creator>person</dc:creator>
		<pubDate>Wed, 15 Jul 2009 17:53:04 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1034</guid>
		<description>That prefix mozilla adds is not just a good idea, I believe it&#039;s a part of the standard by now. Opera and Safari also follow this convention at the least.
See: http://lists.w3.org/Archives/Public/www-style/2002Jan/0094.html

Note the alternative given of using &quot;_&quot; instead of &quot;-&quot; if your library doesn&#039;t support leading dashes.</description>
		<content:encoded><![CDATA[<p>That prefix mozilla adds is not just a good idea, I believe it&#8217;s a part of the standard by now. Opera and Safari also follow this convention at the least.<br />
See: <a href="http://lists.w3.org/Archives/Public/www-style/2002Jan/0094.html" rel="nofollow">http://lists.w3.org/Archives/Public/www-style/2002Jan/0094.html</a></p>
<p>Note the alternative given of using &#8220;_&#8221; instead of &#8220;-&#8221; if your library doesn&#8217;t support leading dashes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier Samyn</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1031</link>
		<dc:creator>Olivier Samyn</dc:creator>
		<pubDate>Wed, 15 Jul 2009 13:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1031</guid>
		<description>When parsing those CSS files, there should be some available constants (I do not know how to implement this, but it has been discussed for inclusion in CSS3; http://disruptive-innovations.com/zoo/cssvariables/ ).

Some constants should be used for standard colors; but other one used for file names. For example, the application icon should be stored in a variable. so that specifying it as some background, or pixmap border is possible (and then, you may implement the Atlanta theme).

Also, border rounding is defined in CSS3, and supported by modern browsers through extensions (ex: -moz-border radius)
http://www.w3.org/TR/2008/WD-css3-background-20080910/#the-border-radius</description>
		<content:encoded><![CDATA[<p>When parsing those CSS files, there should be some available constants (I do not know how to implement this, but it has been discussed for inclusion in CSS3; <a href="http://disruptive-innovations.com/zoo/cssvariables/" rel="nofollow">http://disruptive-innovations.com/zoo/cssvariables/</a> ).</p>
<p>Some constants should be used for standard colors; but other one used for file names. For example, the application icon should be stored in a variable. so that specifying it as some background, or pixmap border is possible (and then, you may implement the Atlanta theme).</p>
<p>Also, border rounding is defined in CSS3, and supported by modern browsers through extensions (ex: -moz-border radius)<br />
<a href="http://www.w3.org/TR/2008/WD-css3-background-20080910/#the-border-radius" rel="nofollow">http://www.w3.org/TR/2008/WD-css3-background-20080910/#the-border-radius</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin</title>
		<link>http://blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/comment-page-1/#comment-1030</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Wed, 15 Jul 2009 09:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=606#comment-1030</guid>
		<description>What&#039;s your opinion of the client-side-decorations branch [1] in gtk+?

[1] http://git.gnome.org/cgit/gtk+/log/?h=client-side-decorations</description>
		<content:encoded><![CDATA[<p>What&#8217;s your opinion of the client-side-decorations branch [1] in gtk+?</p>
<p>[1] <a href="http://git.gnome.org/cgit/gtk+/log/?h=client-side-decorations" rel="nofollow">http://git.gnome.org/cgit/gtk+/log/?h=client-side-decorations</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/metacity/2009/07/15/copper-an-experiment-with-css/feed/ ) in 1.20499 seconds, on Feb 12th, 2012 at 4:15 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 12th, 2012 at 5:15 am UTC -->
