<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/tag/technique css">
<title>Public marks with tag &quot;technique css&quot;</title>
<description>Public marks with tag &quot;technique css&quot;</description>
<link>http://blogmarks.net/marks/tag/technique css</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/tonio78/mark/1058332195"/>
<rdf:li resource="http://blogmarks.net/api/user/redyrod/mark/1840136"/>
<rdf:li resource="http://blogmarks.net/api/user/redyrod/mark/1840132"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/tonio78/mark/1058332195">
<title>Une technique CSS sympa de Google</title>
<link>http://libre-d-esprit.thinking-days.net/2009/04/une-technique-css-sympa-de-google/</link>
<description>Les feuilles de styles des thèmes iGoogle sont souvent assez innovantes. L’espace horizontal de la page est occupé à 100% quelque soit la résolution de l’écran. Malgré l’absence de fond uni, l’espace est occupé par des images régulièrement espacées avec de légères variations. Il ne s’agit donc pas d’un simple fond répété.

J’ai donc fait un peu “d’ingénierie inverse” sur certains thèmes d’iGoogle pour comprendre comment cela est réalisé. Cette technique ne concerne pas uniquement l’intégration XHTML/CSS. Pour concevoir ce type de page, il faut instaurer un véritable échange créatif entre les artistes, et les techniciens, ce qui manque à mon avis souvent.</description>
<dc:date>2009-05-21T22:32:03Z</dc:date>
<dc:author>tonio78</dc:author>
<dc:subject>technique css, css, xhtml, intégration, google, igoogle</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://libre-d-esprit.thinking-days.net/2009/04/une-technique-css-sympa-de-google/"><img border="0" src="http://blogmarks.net/screenshots/2009/05/21/1d9e3806585bb805c573306b701c3251.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://libre-d-esprit.thinking-days.net/2009/04/une-technique-css-sympa-de-google/">Une technique CSS sympa de Google</a></h4>
 
by <a href="http://blogmarks.net/user/tonio78">tonio78</a> 
<p class="description">Les feuilles de styles des thèmes iGoogle sont souvent assez innovantes. L’espace horizontal de la page est occupé à 100% quelque soit la résolution de l’écran. Malgré l’absence de fond uni, l’espace est occupé par des images régulièrement espacées avec de légères variations. Il ne s’agit donc pas d’un simple fond répété.

J’ai donc fait un peu “d’ingénierie inverse” sur certains thèmes d’iGoogle pour comprendre comment cela est réalisé. Cette technique ne concerne pas uniquement l’intégration XHTML/CSS. Pour concevoir ce type de page, il faut instaurer un véritable échange créatif entre les artistes, et les techniciens, ce qui manque à mon avis souvent.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/technique%2Bcss">technique css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xhtml">xhtml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/int%25C3%25A9gration">intégration</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/igoogle">igoogle</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058332195">Copy</a> | 
<a href="http://blogmarks.net/link/3203521">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/redyrod/mark/1840136">
<title>53 CSS-Techniques You Couldn’t Live Without</title>
<link>http://www.smashingmagazine.com/2007/01/19/53-css-techniques-you-couldnt-live-without/</link>
<description>CSS is important. And it is being used more and more often. Cascading Style Sheets offer many advantages you don’t have in table-layouts - and first of all a strict separation between layout, or design of the page, and the information, presented on the page. Thus the design of pages can be easily changed, just replacing a css-file with another one. Isn’t it great? Well, actualy, it is.</description>
<dc:date>2007-01-25T08:47:28Z</dc:date>
<dc:author>redyrod</dc:author>
<dc:subject>technique css</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.smashingmagazine.com/2007/01/19/53-css-techniques-you-couldnt-live-without/"><img border="0" src="http://blogmarks.net/screenshots/2009/04/28/bb58c50beb6cbbeca8eff62b64518688.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.smashingmagazine.com/2007/01/19/53-css-techniques-you-couldnt-live-without/">53 CSS-Techniques You Couldn’t Live Without</a></h4>
 
by <a href="http://blogmarks.net/user/redyrod">redyrod</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1548277">65 other(s)</a> 
<p class="description">CSS is important. And it is being used more and more often. Cascading Style Sheets offer many advantages you don’t have in table-layouts - and first of all a strict separation between layout, or design of the page, and the information, presented on the page. Thus the design of pages can be easily changed, just replacing a css-file with another one. Isn’t it great? Well, actualy, it is.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/technique%2Bcss">technique css</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1840136">Copy</a> | 
<a href="http://blogmarks.net/link/1548277">React (1)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/redyrod/mark/1840132">
<title>Welcome to Newt Edge</title>
<link>http://phoenity.com/newtedge/</link>
<description>This Newt Edge site is created not for the faint-hearted browsers, but more specifically to highly standards compliant browsers, such as Gecko-based browsers. This site is the place for my collections of markup test cases, style sheets demonstrations and coding workarounds. Feel free to browse around and experience my work.</description>
<dc:date>2007-01-25T08:46:44Z</dc:date>
<dc:author>redyrod</dc:author>
<dc:subject>technique css</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://phoenity.com/newtedge/"><img border="0" src="http://blogmarks.net/screenshots/2007/01/25/430db1fd42fd41cf3e381b507adb0d2a.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://phoenity.com/newtedge/">Welcome to Newt Edge</a></h4>
 
by <a href="http://blogmarks.net/user/redyrod">redyrod</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/54554">2 other(s)</a> 
<p class="description">This Newt Edge site is created not for the faint-hearted browsers, but more specifically to highly standards compliant browsers, such as Gecko-based browsers. This site is the place for my collections of markup test cases, style sheets demonstrations and coding workarounds. Feel free to browse around and experience my work.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/technique%2Bcss">technique css</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1840132">Copy</a> | 
<a href="http://blogmarks.net/link/54554">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>