<?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/search/browsers">
<title>Public marks with search browsers</title>
<description>Public marks with search browsers</description>
<link>http://blogmarks.net/marks/search/browsers</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/marco/mark/1058628882"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058627292"/>
<rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1058627133"/>
<rdf:li resource="http://blogmarks.net/api/user/naudjf/mark/1058617568"/>
<rdf:li resource="http://blogmarks.net/api/user/delavigne/mark/1058608800"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596119"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596120"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596153"/>
<rdf:li resource="http://blogmarks.net/api/user/philippej/mark/1058587775"/>
<rdf:li resource="http://blogmarks.net/api/user/srcmax/mark/1058586380"/>
<rdf:li resource="http://blogmarks.net/api/user/sbrothier/mark/1058586375"/>
<rdf:li resource="http://blogmarks.net/api/user/vrossign/mark/1058586288"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058582349"/>
<rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1058580404"/>
<rdf:li resource="http://blogmarks.net/api/user/dzc/mark/1058571250"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596363"/>
<rdf:li resource="http://blogmarks.net/api/user/srcmax/mark/1058567721"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596369"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596373"/>
<rdf:li resource="http://blogmarks.net/api/user/nicolargo/mark/1058564734"/>
<rdf:li resource="http://blogmarks.net/api/user/mozkart/mark/1058564187"/>
<rdf:li resource="http://blogmarks.net/api/user/oseres/mark/1058563800"/>
<rdf:li resource="http://blogmarks.net/api/user/yafundy/mark/1058563651"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596414"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596422"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/marco/mark/1058628882">
<title>Why the HTML5 'Video' Element Is Effectively Unusable, Even in Browsers Which Support It</title>
<link>http://daringfireball.net/2009/12/html5_video_unusable</link>
<description></description>
<dc:date>2009-12-23T15:32:56Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>html5, video</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://daringfireball.net/2009/12/html5_video_unusable"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://daringfireball.net/2009/12/html5_video_unusable">Why the HTML5 'Video' Element Is Effectively Unusable, Even in Browsers Which Support It</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3444561">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/video">video</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058628882">Copy</a> | 
<a href="http://blogmarks.net/link/3444561">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058627292">
<title>[whatwg] Inconsistent behavior for empty-string URLs</title>
<link>http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-December/024622.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;results of testing various tags with empty URLs across different browsers.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-12-22T03:10:09Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>testing, uri, browser, interoperability</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-December/024622.html"><img border="0" src="http://blogmarks.net/screenshots/2009/12/22/6e4b67289081f552b7aafa71347fdecf.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-December/024622.html">[whatwg] Inconsistent behavior for empty-string URLs</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>results of testing various tags with empty URLs across different browsers.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/testing">testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/uri">uri</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browser">browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/interoperability">interoperability</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058627292">Copy</a> | 
<a href="http://blogmarks.net/link/3444686">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1058627133">
<title>Daring Fireball: Why the HTML5 'Video' Element Is Effectively Unusable, Even in the Browsers Which Support It</title>
<link>http://daringfireball.net/2009/12/html5_video_unusable</link>
<description>&lt;blockquote&gt;&lt;p&gt;The bad news: In all three browsers (Safari, Chrome, Firefox), with the above simple markup, the video content buffers automatically on page load. What I mean is that as soon as you load the web page, the browsers download the actual video files that are embedded&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Moi qui pensait que &amp;lt;audio&amp;gt; et &amp;lt;video&amp;gt; étaient prag-ma-ti-ques. Mais non, après des semaines de débats sur les formats à supporter (ou non), les ultra-géniaux (et modestes) concepteurs de HTML 5 ont laissé un élément de base d'utilisabilité de côté. Comme quoi, les mailing-list du WHAT WG auraient dû être bannies à Copenhague.&lt;/p&gt;</description>
<dc:date>2009-12-21T22:07:11Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>html5, pragmatisme</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://daringfireball.net/2009/12/html5_video_unusable"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://daringfireball.net/2009/12/html5_video_unusable">Daring Fireball: Why the HTML5 'Video' Element Is Effectively Unusable, Even in the Browsers Which Support It</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3444561">1 other(s)</a> 
<div class="description"><blockquote><p>The bad news: In all three browsers (Safari, Chrome, Firefox), with the above simple markup, the video content buffers automatically on page load. What I mean is that as soon as you load the web page, the browsers download the actual video files that are embedded</p></blockquote>
<p>Moi qui pensait que &lt;audio&gt; et &lt;video&gt; étaient prag-ma-ti-ques. Mais non, après des semaines de débats sur les formats à supporter (ou non), les ultra-géniaux (et modestes) concepteurs de HTML 5 ont laissé un élément de base d'utilisabilité de côté. Comme quoi, les mailing-list du WHAT WG auraient dû être bannies à Copenhague.</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pragmatisme">pragmatisme</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058627133">Copy</a> | 
<a href="http://blogmarks.net/link/3444561">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/naudjf/mark/1058617568">
<title> 	Disaboom on Top 8 Free Browsers for Seniors and Disabled</title>
<link>http://blog.brightstarhealthcare.com/bid/27533/Assistive-Technology-Top-8-Free-Browsers-for-Visual-Impairment-and-More</link>
<description></description>
<dc:date>2009-12-11T14:15:56Z</dc:date>
<dc:author>naudjf</dc:author>
<dc:subject>disabled, Disaboom, seniors, Top 8, browsers, free</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.brightstarhealthcare.com/bid/27533/Assistive-Technology-Top-8-Free-Browsers-for-Visual-Impairment-and-More"><img border="0" src="http://blogmarks.net/screenshots/2009/12/11/814e3b292f070bed98e07c40246a2e9a.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.brightstarhealthcare.com/bid/27533/Assistive-Technology-Top-8-Free-Browsers-for-Visual-Impairment-and-More"> 	Disaboom on Top 8 Free Browsers for Seniors and Disabled</a></h4>
 
by <a href="http://blogmarks.net/user/naudjf">naudjf</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/disabled">disabled</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Disaboom">Disaboom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/seniors">seniors</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Top%2B8">Top 8</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browsers">browsers</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/free">free</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058617568">Copy</a> | 
<a href="http://blogmarks.net/link/3436695">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/delavigne/mark/1058608800">
<title>jParse - jQuery XML Parse Plugin</title>
<link>http://jparse.kylerush.net/</link>
<description>jParse is a jQuery plugin that allows you to parse XML that was fetched with the jQuery .ajax method (making it fully customizable). It's easy to use and ultra lightweight at only 2.49KB! Best of all, it's compatible with all major browsers:</description>
<dc:date>2009-12-04T00:08:17Z</dc:date>
<dc:author>delavigne</dc:author>
<dc:subject>plugin, xml, jQuery, tools</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://jparse.kylerush.net/"><img border="0" src="http://blogmarks.net/screenshots/2009/12/04/60046c1ee66889e7d19e216cf4e8b568.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://jparse.kylerush.net/">jParse - jQuery XML Parse Plugin</a></h4>
 
by <a href="http://blogmarks.net/user/delavigne">delavigne</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3404977">2 other(s)</a> 
<p class="description">jParse is a jQuery plugin that allows you to parse XML that was fetched with the jQuery .ajax method (making it fully customizable). It's easy to use and ultra lightweight at only 2.49KB! Best of all, it's compatible with all major browsers:</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/plugin">plugin</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/jQuery">jQuery</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058608800">Copy</a> | 
<a href="http://blogmarks.net/link/3404977">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596119">
<title>Timeline of web browsers - Wikipedia, the free encyclopedia</title>
<link>http://en.wikipedia.org/wiki/Timeline_of_web_browsers#Graphical_Timeline</link>
<description></description>
<dc:date>2009-11-28T08:23:57Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>browsers, history, timeline</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://en.wikipedia.org/wiki/Timeline_of_web_browsers#Graphical_Timeline"><img border="0" src="http://blogmarks.net/screenshots/2009/11/28/7475feaae1255aba209e5b27e3b98468.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://en.wikipedia.org/wiki/Timeline_of_web_browsers#Graphical_Timeline">Timeline of web browsers - Wikipedia, the free encyclopedia</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browsers">browsers</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/history">history</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/timeline">timeline</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596119">Copy</a> | 
<a href="http://blogmarks.net/link/3419696">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596120">
<title>What Browser? - Home</title>
<link>http://www.whatbrowser.org/</link>
<description>A few of us at Google created WhatBrowser.org to help teach people about web browsers. We wanted to show people that they have a lot of choice in browsers, since we noticed that most people were using the browser their computers came with.</description>
<dc:date>2009-11-28T08:19:48Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>browser, whatis</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.whatbrowser.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/11/28/7d21cb3fbb1c645581523f9d4e42e78b.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.whatbrowser.org/">What Browser? - Home</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="description">A few of us at Google created WhatBrowser.org to help teach people about web browsers. We wanted to show people that they have a lot of choice in browsers, since we noticed that most people were using the browser their computers came with.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browser">browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/whatis">whatis</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596120">Copy</a> | 
<a href="http://blogmarks.net/link/3419697">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596153">
<title>Learn More About Our Revolutionary Online Payment and Shopping Cart Platform</title>
<link>http://www.trialpay.com/</link>
<description>TrialPay’s unique e-commerce solutions increase the probability of conversion and maximize the profit of each transaction:      *       Get It Free        For browsers who don't plan on buying, TrialPay provides thousands of ways to Get It Free by completing one offer from premier brands.     *       Purchase Incentives        For shoppers who are contemplating a purchase, Purchase Incentives provide a compelling reason to follow through.     *       Transaction Ads        Transaction Ads provide free brand exposure and pay-for-performance advertising to create the most cost-effective model available.</description>
<dc:date>2009-11-21T19:07:14Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>trial, embed, service, ecommerce, shopping</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.trialpay.com/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.trialpay.com/">Learn More About Our Revolutionary Online Payment and Shopping Cart Platform</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="description">TrialPay’s unique e-commerce solutions increase the probability of conversion and maximize the profit of each transaction:      *       Get It Free        For browsers who don't plan on buying, TrialPay provides thousands of ways to Get It Free by completing one offer from premier brands.     *       Purchase Incentives        For shoppers who are contemplating a purchase, Purchase Incentives provide a compelling reason to follow through.     *       Transaction Ads        Transaction Ads provide free brand exposure and pay-for-performance advertising to create the most cost-effective model available.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/trial">trial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/embed">embed</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/service">service</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ecommerce">ecommerce</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/shopping">shopping</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596153">Copy</a> | 
<a href="http://blogmarks.net/link/3419718">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/philippej/mark/1058587775">
<title>Video for Everybody!</title>
<link>http://camendesign.com/code/video_for_everybody</link>
<description>&quot;Video for Everybody is very simply a chunk of HTML code that embeds a video into a website using the HTML5 &amp;lt;video&amp;gt; element which offers native playback in Firefox 3.5, Safari 3 &amp;amp; 4, Google Chrome and an increasing number of other browsers: &quot;</description>
<dc:date>2009-11-20T21:17:38Z</dc:date>
<dc:author>philippej</dc:author>
<dc:subject>video, webdesign, html, navigateurs</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://camendesign.com/code/video_for_everybody"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://camendesign.com/code/video_for_everybody">Video for Everybody!</a></h4>
 
by <a href="http://blogmarks.net/user/philippej">philippej</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3271017">3 other(s)</a> 
<p class="description">"Video for Everybody is very simply a chunk of HTML code that embeds a video into a website using the HTML5 &lt;video&gt; element which offers native playback in Firefox 3.5, Safari 3 &amp; 4, Google Chrome and an increasing number of other browsers: "</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/video">video</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdesign">webdesign</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/navigateurs">navigateurs</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058587775">Copy</a> | 
<a href="http://blogmarks.net/link/3271017">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/srcmax/mark/1058586380">
<title>Browser Testing: Test Your Websites on All Major Browsers - Litmus</title>
<link>http://litmusapp.com/browser-testing</link>
<description>&lt;blockquote&gt;
&lt;p&gt;Browser testing&lt;/p&gt;
&lt;p&gt;Work faster. Impress your clients. Test your website designs across all major browsers in seconds with Litmus.&lt;/p&gt;
&lt;/blockquote&gt;</description>
<dc:date>2009-11-19T10:12:50Z</dc:date>
<dc:author>srcmax</dc:author>
<dc:subject>integration, test, browser, emailing</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://litmusapp.com/browser-testing"><img border="0" src="http://blogmarks.net/screenshots/2009/11/19/b96f6a570bc272a528a9d4acf55d3a7d.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://litmusapp.com/browser-testing">Browser Testing: Test Your Websites on All Major Browsers - Litmus</a></h4>
 
by <a href="http://blogmarks.net/user/srcmax">srcmax</a> 
<div class="description"><blockquote>
<p>Browser testing</p>
<p>Work faster. Impress your clients. Test your website designs across all major browsers in seconds with Litmus.</p>
</blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/integration">integration</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/test">test</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browser">browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/emailing">emailing</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058586380">Copy</a> | 
<a href="http://blogmarks.net/link/3172717">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/sbrothier/mark/1058586375">
<title>Browser Testing: Test Your Websites on All Major Browsers - Litmus</title>
<link>http://litmusapp.com/browser-testing?referrer=wfs</link>
<description>Work faster. Impress your clients. Test your website designs across all major browsers in seconds with Litmus.</description>
<dc:date>2009-11-19T10:02:02Z</dc:date>
<dc:author>sbrothier</dc:author>
<dc:subject>webdesign, web/tech, web services</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://litmusapp.com/browser-testing?referrer=wfs"><img border="0" src="http://blogmarks.net/screenshots/2009/11/19/913c3ed0b7f871031f7a2d803b50d334.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://litmusapp.com/browser-testing?referrer=wfs">Browser Testing: Test Your Websites on All Major Browsers - Litmus</a></h4>
 
by <a href="http://blogmarks.net/user/sbrothier">sbrothier</a> 
<p class="description">Work faster. Impress your clients. Test your website designs across all major browsers in seconds with Litmus.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdesign">webdesign</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web%252Ftech">web/tech</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web%2Bservices">web services</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058586375">Copy</a> | 
<a href="http://blogmarks.net/link/3411616">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/vrossign/mark/1058586288">
<title>Site-Specific Browsers: Turn Websites Into Desktop Applications</title>
<link>http://www.webresourcesdepot.com/site-specific-browsers-turn-websites-into-desktop-applications/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed: webresourcesdepot (WebResourcesDepot)&amp;utm_content=Netvibes</link>
<description></description>
<dc:date>2009-11-19T08:20:23Z</dc:date>
<dc:author>vrossign</dc:author>
<dc:subject>web, apps, appli, lourd</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.webresourcesdepot.com/site-specific-browsers-turn-websites-into-desktop-applications/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed: webresourcesdepot (WebResourcesDepot)&amp;utm_content=Netvibes"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.webresourcesdepot.com/site-specific-browsers-turn-websites-into-desktop-applications/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed: webresourcesdepot (WebResourcesDepot)&amp;utm_content=Netvibes">Site-Specific Browsers: Turn Websites Into Desktop Applications</a></h4>
 
by <a href="http://blogmarks.net/user/vrossign">vrossign</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apps">apps</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/appli">appli</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lourd">lourd</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058586288">Copy</a> | 
<a href="http://blogmarks.net/link/3411543">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058582349">
<title>Correct way to handle mobile browsers | Surfing in Kansas</title>
<link>http://ericholscher.com/blog/2009/nov/9/correct-way-handle-mobile-browsers/</link>
<description>&lt;blockquote&gt;&lt;p&gt;Minidetector is a Django reusable app that allows you to know if a request is being viewed on a mobile device. It provides a middleware and a view decorator that sets a request.mobile variable to True if the request is coming from a mobile device. It's method of figuring out if a device is mobile is simple; It first checks for a special Opera Mini header, then for WAP support, then finally checks the User Agent against a list of known mobile strings.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-15T11:59:47Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>mobile, django, python</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://ericholscher.com/blog/2009/nov/9/correct-way-handle-mobile-browsers/"><img border="0" src="http://blogmarks.net/screenshots/2009/11/15/1d059549fd9b9ff4a67a8aa89603a6b8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://ericholscher.com/blog/2009/nov/9/correct-way-handle-mobile-browsers/">Correct way to handle mobile browsers | Surfing in Kansas</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Minidetector is a Django reusable app that allows you to know if a request is being viewed on a mobile device. It provides a middleware and a view decorator that sets a request.mobile variable to True if the request is coming from a mobile device. It's method of figuring out if a device is mobile is simple; It first checks for a special Opera Mini header, then for WAP support, then finally checks the User Agent against a list of known mobile strings.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mobile">mobile</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/django">django</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/python">python</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058582349">Copy</a> | 
<a href="http://blogmarks.net/link/3408590">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1058580404">
<title>Michael(tm) Smith » WebKit adds support for the HTML5 &lt;ruby&gt; element</title>
<link>http://sideshowbarker.net/2009/11/13/html5-ruby/</link>
<description>&lt;blockquote&gt;&lt;p&gt;Current versions of Microsoft Internet Explorer also have native support for ruby, and you can also get ruby support in Firefox by installing Piro’s XHTML Ruby add-on (and for more details, see his XHTML ruby add-on info page) — so we are well on the way to seeing the HTML5 ruby feature supported across a range of browsers.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Maintenant que Ruby a gagné son petit autocollant &quot;HTML 5&quot;, les développeurs de navigateurs s'y intéressent. Comme quoi, le web tient à peu de chose.&lt;/p&gt;</description>
<dc:date>2009-11-13T10:14:02Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>html5, fayots</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://sideshowbarker.net/2009/11/13/html5-ruby/"><img border="0" src="http://blogmarks.net/screenshots/2009/11/13/788d0958a92bdce06013d6a03ee6c048.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://sideshowbarker.net/2009/11/13/html5-ruby/">Michael(tm) Smith » WebKit adds support for the HTML5 &lt;ruby&gt; element</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
<div class="description"><blockquote><p>Current versions of Microsoft Internet Explorer also have native support for ruby, and you can also get ruby support in Firefox by installing Piro’s XHTML Ruby add-on (and for more details, see his XHTML ruby add-on info page) — so we are well on the way to seeing the HTML5 ruby feature supported across a range of browsers.</p></blockquote>
<p>Maintenant que Ruby a gagné son petit autocollant "HTML 5", les développeurs de navigateurs s'y intéressent. Comme quoi, le web tient à peu de chose.</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fayots">fayots</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058580404">Copy</a> | 
<a href="http://blogmarks.net/link/3406952">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/dzc/mark/1058571250">
<title>Overcome Your Caching Conundrums [Server Side Essentials]</title>
<link>http://articles.sitepoint.com/article/overcome-cache-conundrums</link>
<description>ealing with browser caching is a balancing act. On one hand, you aim to minimize load times and bandwidth use by ensuring that images, scripts, and style sheets are cached by your visitors; however, you still want to ensure that they’re accessing the most recent versions of all your files.

In this article, I’ll show you a few methods for controlling how your site’s files are cached by browsers so you can achieve the best of both worlds: maintaining optimal performance while ensuring that any updates are seen immediately, without a hitch by all of your users.</description>
<dc:date>2009-11-03T15:34:24Z</dc:date>
<dc:author>dzc</dc:author>
<dc:subject>css, image, performance, optimisation, conception web, cache, navigateur</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://articles.sitepoint.com/article/overcome-cache-conundrums"><img border="0" src="http://blogmarks.net/screenshots/2009/11/03/a58cbae6863e4ccdc981f58955828305.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://articles.sitepoint.com/article/overcome-cache-conundrums">Overcome Your Caching Conundrums [Server Side Essentials]</a></h4>
 
by <a href="http://blogmarks.net/user/dzc">dzc</a> 
<p class="description">ealing with browser caching is a balancing act. On one hand, you aim to minimize load times and bandwidth use by ensuring that images, scripts, and style sheets are cached by your visitors; however, you still want to ensure that they’re accessing the most recent versions of all your files.

In this article, I’ll show you a few methods for controlling how your site’s files are cached by browsers so you can achieve the best of both worlds: maintaining optimal performance while ensuring that any updates are seen immediately, without a hitch by all of your users.</p>
<p class="tags">
<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/image">image</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optimisation">optimisation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/conception%2Bweb">conception web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/navigateur">navigateur</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058571250">Copy</a> | 
<a href="http://blogmarks.net/link/3399935">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596363">
<title>UniView 5.1.0 (© Richard Ishida)</title>
<link>http://rishida.net/scripts/uniview</link>
<description>What is UniView?  An XHTML-based application to look up characters, character blocks, paste in and discover unknown characters, search for characters, do hex/dec/ncr conversions, highlight character types, etc. etc.  It supports Unicode 5.2(beta) and is written with Web Standards to work on all major browsers. It is based on XHTML, JavaScript, PHP and AJAX technologies, so you don't need to download anything. How do I use it?  I suggest you check out the help file for instructions and new features first.  Then just go to the UniView page. Note that you must have JavaScript enabled.  Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Frishida.net%2Fscripts%2Funiview</description>
<dc:date>2009-10-30T13:41:02Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>unicode, advanced, tools, converter</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://rishida.net/scripts/uniview"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://rishida.net/scripts/uniview">UniView 5.1.0 (© Richard Ishida)</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="description">What is UniView?  An XHTML-based application to look up characters, character blocks, paste in and discover unknown characters, search for characters, do hex/dec/ncr conversions, highlight character types, etc. etc.  It supports Unicode 5.2(beta) and is written with Web Standards to work on all major browsers. It is based on XHTML, JavaScript, PHP and AJAX technologies, so you don't need to download anything. How do I use it?  I suggest you check out the help file for instructions and new features first.  Then just go to the UniView page. Note that you must have JavaScript enabled.  Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Frishida.net%2Fscripts%2Funiview</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unicode">unicode</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/advanced">advanced</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/converter">converter</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596363">Copy</a> | 
<a href="http://blogmarks.net/link/3419864">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/srcmax/mark/1058567721">
<title>Google Chrome Blog: Bringing Google Sidewiki goodness to Google Chrome, Part I</title>
<link>http://chrome.blogspot.com/2009/10/bringing-google-sidewiki-goodness-to.html</link>
<description>&lt;blockquote&gt;
&lt;p&gt;Until now, Sidewiki was available only through Google Toolbar for Firefox and Internet Explorer. Today, we're excited to release the official bookmarklet for Sidewiki, which lets you easily read and write Sidewiki entries in Google Chrome, Safari and others browsers.&lt;/p&gt;
&lt;/blockquote&gt;</description>
<dc:date>2009-10-30T13:39:26Z</dc:date>
<dc:author>srcmax</dc:author>
<dc:subject>google sidewiki, bookmarklet</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://chrome.blogspot.com/2009/10/bringing-google-sidewiki-goodness-to.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/30/f703bb564ef90d13125cc3e5ec74b2a8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://chrome.blogspot.com/2009/10/bringing-google-sidewiki-goodness-to.html">Google Chrome Blog: Bringing Google Sidewiki goodness to Google Chrome, Part I</a></h4>
 
by <a href="http://blogmarks.net/user/srcmax">srcmax</a> 
<div class="description"><blockquote>
<p>Until now, Sidewiki was available only through Google Toolbar for Firefox and Internet Explorer. Today, we're excited to release the official bookmarklet for Sidewiki, which lets you easily read and write Sidewiki entries in Google Chrome, Safari and others browsers.</p>
</blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google%2Bsidewiki">google sidewiki</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bookmarklet">bookmarklet</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058567721">Copy</a> | 
<a href="http://blogmarks.net/link/3396991">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596369">
<title>Adobe® BrowserLab</title>
<link>https://browserlab.adobe.com/index.html</link>
<description>Adobe BrowerLab gives you the ability to preview and test your websites in multiple browsers and operating systems. Since building a website to be cross-browser compatible is one of the more annoying aspects of web design, this should be a valuable web app to all of us.</description>
<dc:date>2009-10-29T15:11:16Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>browser, preview, tester, online, tools, webdesigner</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="https://browserlab.adobe.com/index.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="https://browserlab.adobe.com/index.html">Adobe® BrowserLab</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="description">Adobe BrowerLab gives you the ability to preview and test your websites in multiple browsers and operating systems. Since building a website to be cross-browser compatible is one of the more annoying aspects of web design, this should be a valuable web app to all of us.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browser">browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/preview">preview</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tester">tester</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/online">online</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdesigner">webdesigner</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596369">Copy</a> | 
<a href="http://blogmarks.net/link/3419867">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596373">
<title>Selenium web application testing system</title>
<link>http://seleniumhq.org/</link>
<description>Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language. Selenium provides a test domain specific language (DSL) to write tests in a number of popular programming languages, including Java, Ruby, Groovy, Python, PHP, and Perl. Test playback is in most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.  Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Fseleniumhq.org</description>
<dc:date>2009-10-29T13:12:41Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>opensource, software, webdev, test, tools, webapps</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://seleniumhq.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/11/f9d870119540f7b4a06c050eacdbb5e6.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://seleniumhq.org/">Selenium web application testing system</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3066935">3 other(s)</a> 
<p class="description">Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language. Selenium provides a test domain specific language (DSL) to write tests in a number of popular programming languages, including Java, Ruby, Groovy, Python, PHP, and Perl. Test playback is in most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.  Annotated link http://www.diigo.com/bookmark/http%3A%2F%2Fseleniumhq.org</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opensource">opensource</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software">software</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdev">webdev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/test">test</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webapps">webapps</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596373">Copy</a> | 
<a href="http://blogmarks.net/link/3066935">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/nicolargo/mark/1058564734">
<title>Top 5 Browsers from Sep 08 to Oct 09 | StatCounter Global Stats</title>
<link>http://gs.statcounter.com/</link>
<description>Statistique utilisation des navigateurs Web (thx Martin Erpicum)</description>
<dc:date>2009-10-27T15:42:37Z</dc:date>
<dc:author>nicolargo</dc:author>
<dc:subject>navigateur, stats</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://gs.statcounter.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/27/34685bd943799072938bcab45ab3d98e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://gs.statcounter.com/">Top 5 Browsers from Sep 08 to Oct 09 | StatCounter Global Stats</a></h4>
 
by <a href="http://blogmarks.net/user/nicolargo">nicolargo</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3127457">3 other(s)</a> 
<p class="description">Statistique utilisation des navigateurs Web (thx Martin Erpicum)</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/navigateur">navigateur</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/stats">stats</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058564734">Copy</a> | 
<a href="http://blogmarks.net/link/3127457">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mozkart/mark/1058564187">
<title>Top reasons your CSS columns are messed up - Warpspire 	    	</title>
<link>http://warpspire.com/tipsresources/web-production/css-column-tricks/</link>
<description>I believe the recent surge in popularity of CSS frameworks comes from a lack of basic understanding of the CSS box model and how it’s implemented across browsers. I wanted to share with you some quick tips on how to avoid easy pitfalls so you can create your own CSS framework in no time flat, without all the cruft of having ten thousand column combinations available. Keeping these quick tips in mind at all times will allow you to do something I like to call defensive coding — and really that’s all CSS frameworks are: defensively coded snippets of CSS.

</description>
<dc:date>2009-10-27T00:04:55Z</dc:date>
<dc:author>mozkart</dc:author>
<dc:subject>css</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://warpspire.com/tipsresources/web-production/css-column-tricks/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/27/f8534f5564d94870459b7d0e18d44a4e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://warpspire.com/tipsresources/web-production/css-column-tricks/">Top reasons your CSS columns are messed up - Warpspire 	    	</a></h4>
 
by <a href="http://blogmarks.net/user/mozkart">mozkart</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2784693">1 other(s)</a> 
<p class="description">I believe the recent surge in popularity of CSS frameworks comes from a lack of basic understanding of the CSS box model and how it’s implemented across browsers. I wanted to share with you some quick tips on how to avoid easy pitfalls so you can create your own CSS framework in no time flat, without all the cruft of having ten thousand column combinations available. Keeping these quick tips in mind at all times will allow you to do something I like to call defensive coding — and really that’s all CSS frameworks are: defensively coded snippets of CSS.

</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058564187">Copy</a> | 
<a href="http://blogmarks.net/link/2784693">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/oseres/mark/1058563800">
<title>Creating Offline Web Applicat...</title>
<link>http://docs.google.com/View?docid=dhkhksk4_8gdp9gr#sync</link>
<description>Creating Offline Web Applications With Dojo Offline

by Brad Neuberg (SitePen), September 23rd, 2007

This tutorial steps you through creating offline web applications using Dojo Offline.
What is Dojo Offline?

Dojo Offline is an open-source toolkit that makes it easy to create sophisticated, offline web applications. It sits on top of Google Gears, a plugin from Google that helps extend web browsers with new functionality. Dojo Offline makes working with Google Gears easier; extends it with important functionality; creates a higher-level API than Google Gears provides; and exposes developer productivity features. In particular, Dojo Offline provides the following functionality:

An offline widget that you can easily embed in your web page with just a few lines of code, automatically providing the user with network feedback, sync messages, offline instructions, and more
A sync framework to help you store actions done while offline and sync them with a server once back on the network
Automatic network and application-availability detection to determine when your application is on- or off-line so that you can take appropriate action
A slurp() method that automatically scans the page and figures out all the resources that you need offline, including images, stylesheets, scripts, etc.; this is much easier than having to manually maintain which resources should be available offline, especially during development.
Dojo Storage, an easy to use hashtable abstraction for storing offline data for when you don't need the heaviness of Google Gear's SQL abstraction; under the covers Dojo Storage saves its data into Google Gears
Dojo SQL, an easy to use SQL layer that executes SQL statements and returns them as ordinary JavaScript objects
New ENCRYPT() and DECRYPT() SQL keywords that you can mix in when using Dojo SQL, to get transparent cryptography for columns of data. Cryptography is done on a Google Worker Pool thread, so that the browser UI is responsive.
Integration with the rest of Dojo, such as the Dojo Event system
</description>
<dc:date>2009-10-26T12:18:18Z</dc:date>
<dc:author>oseres</dc:author>
<dc:subject>web, google, storage, plugin, browser, sync</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://docs.google.com/View?docid=dhkhksk4_8gdp9gr#sync"><img border="0" src="http://blogmarks.net/screenshots/2009/10/26/6ec0d965b36551c86f02ff03c5f5594a.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://docs.google.com/View?docid=dhkhksk4_8gdp9gr#sync">Creating Offline Web Applicat...</a></h4>
 
by <a href="http://blogmarks.net/user/oseres">oseres</a> 
<p class="description">Creating Offline Web Applications With Dojo Offline

by Brad Neuberg (SitePen), September 23rd, 2007

This tutorial steps you through creating offline web applications using Dojo Offline.
What is Dojo Offline?

Dojo Offline is an open-source toolkit that makes it easy to create sophisticated, offline web applications. It sits on top of Google Gears, a plugin from Google that helps extend web browsers with new functionality. Dojo Offline makes working with Google Gears easier; extends it with important functionality; creates a higher-level API than Google Gears provides; and exposes developer productivity features. In particular, Dojo Offline provides the following functionality:

An offline widget that you can easily embed in your web page with just a few lines of code, automatically providing the user with network feedback, sync messages, offline instructions, and more
A sync framework to help you store actions done while offline and sync them with a server once back on the network
Automatic network and application-availability detection to determine when your application is on- or off-line so that you can take appropriate action
A slurp() method that automatically scans the page and figures out all the resources that you need offline, including images, stylesheets, scripts, etc.; this is much easier than having to manually maintain which resources should be available offline, especially during development.
Dojo Storage, an easy to use hashtable abstraction for storing offline data for when you don't need the heaviness of Google Gear's SQL abstraction; under the covers Dojo Storage saves its data into Google Gears
Dojo SQL, an easy to use SQL layer that executes SQL statements and returns them as ordinary JavaScript objects
New ENCRYPT() and DECRYPT() SQL keywords that you can mix in when using Dojo SQL, to get transparent cryptography for columns of data. Cryptography is done on a Google Worker Pool thread, so that the browser UI is responsive.
Integration with the rest of Dojo, such as the Dojo Event system
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</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/storage">storage</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/plugin">plugin</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browser">browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sync">sync</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058563800">Copy</a> | 
<a href="http://blogmarks.net/link/3393947">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/yafundy/mark/1058563651">
<title>Adobe Browserlab : nouvel outil de tests multi-browsers</title>
<link>http://www.journalduweb20.com/adobe-browserlab-nouvel-outil-de-tests-multi-browsers/</link>
<description>Voici  le nouvel arrivant dans les outils gratuits de test cross-browsers (vérification du rendu du design d’un site sous différents navigateurs) : Browserlab.</description>
<dc:date>2009-10-26T07:01:23Z</dc:date>
<dc:author>yafundy</dc:author>
<dc:subject>design, cross-browser, tests, adobe</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.journalduweb20.com/adobe-browserlab-nouvel-outil-de-tests-multi-browsers/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/26/b1bba39f3c6dd7c07418338a02211750.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.journalduweb20.com/adobe-browserlab-nouvel-outil-de-tests-multi-browsers/">Adobe Browserlab : nouvel outil de tests multi-browsers</a></h4>
 
by <a href="http://blogmarks.net/user/yafundy">yafundy</a> 
<p class="description">Voici  le nouvel arrivant dans les outils gratuits de test cross-browsers (vérification du rendu du design d’un site sous différents navigateurs) : Browserlab.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/design">design</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cross-browser">cross-browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tests">tests</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/adobe">adobe</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058563651">Copy</a> | 
<a href="http://blogmarks.net/link/3393829">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596414">
<title>BrowserPlus™</title>
<link>http://browserplus.yahoo.com/</link>
<description>BrowserPlus™ is a technology for web browsers that allows developers to create rich web applications with desktop capabilities.</description>
<dc:date>2009-10-25T21:06:46Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>yahoo, browser, api, webapps, webdev</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://browserplus.yahoo.com/"><img border="0" src="http://blogmarks.net/screenshots/2008/11/12/3511432ff2669cee9e7a7107906c7647.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://browserplus.yahoo.com/">BrowserPlus™</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2964905">1 other(s)</a> 
<p class="description">BrowserPlus™ is a technology for web browsers that allows developers to create rich web applications with desktop capabilities.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/yahoo">yahoo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browser">browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webapps">webapps</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdev">webdev</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596414">Copy</a> | 
<a href="http://blogmarks.net/link/2964905">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596422">
<title>Surfraw - Shell Users' Revolutionary Front Rage Against the Web</title>
<link>http://surfraw.alioth.debian.org/</link>
<description>Surfraw provides a fast unix command line interface to a variety of popular WWW search engines and other artifacts of power. It reclaims google, altavista, babelfish, dejanews, freshmeat, research index, slashdot and many others from the false-prophet, pox-infested heathen lands of html-forms, placing these wonders where they belong, deep in unix heartland, as god loving extensions to the shell.  Surfraw abstracts the browser away from input. Doing so lets it get on with what it's good at. Browsing. Interpretation of linguistic forms is handed back to the shell, which is what it, and human beings are good at. Combined with netscape-remote or incremental text browsers, such as lynx, links or w3m, along with screen a Surfraw liberateur is capable of navigating speeds that leave GUI tainted idolaters agape with fear and wonder.</description>
<dc:date>2009-10-25T09:37:18Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>yubnub, unix, SearchEngine, debian</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://surfraw.alioth.debian.org/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://surfraw.alioth.debian.org/">Surfraw - Shell Users' Revolutionary Front Rage Against the Web</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="description">Surfraw provides a fast unix command line interface to a variety of popular WWW search engines and other artifacts of power. It reclaims google, altavista, babelfish, dejanews, freshmeat, research index, slashdot and many others from the false-prophet, pox-infested heathen lands of html-forms, placing these wonders where they belong, deep in unix heartland, as god loving extensions to the shell.  Surfraw abstracts the browser away from input. Doing so lets it get on with what it's good at. Browsing. Interpretation of linguistic forms is handed back to the shell, which is what it, and human beings are good at. Combined with netscape-remote or incremental text browsers, such as lynx, links or w3m, along with screen a Surfraw liberateur is capable of navigating speeds that leave GUI tainted idolaters agape with fear and wonder.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/yubnub">yubnub</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unix">unix</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/SearchEngine">SearchEngine</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debian">debian</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596422">Copy</a> | 
<a href="http://blogmarks.net/link/3419903">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>