<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Snipplr - j_junyent</title>
<link>http://snipplr.com/users/j_junyent/language/css</link>
<description>Recent snippets posted on Snipplr.com</description>
<language>en-us</language>
<pubDate>Sun, 12 Oct 2008 04:46:03 GMT</pubDate>
<item>
<title>(CSS) Wordpress Align</title>
<link>http://snipplr.com/view/7778/wordpress-align/</link>
<description><![CDATA[ <p>How to align floating images in wordpress posts and add captions.</p> ]]></description>
<pubDate>Fri, 08 Aug 2008 07:35:21 GMT</pubDate>
<guid>http://snipplr.com/view/7778/wordpress-align/</guid>
</item>
<item>
<title>(CSS) Displaying Code Snippets: Wrap Long Lines with PRE Tag</title>
<link>http://snipplr.com/view/4546/displaying-code-snippets-wrap-long-lines-with-pre-tag/</link>
<description><![CDATA[ <p>The  tag that defines preformatted text is the only tag in HTML that respects and preserves whitespaces like line-breaks, blanks, tabs and multiple spaces between words. Whatever is enclosed inside the pre element will be displayed as-it-is on the web browser.</p> ]]></description>
<pubDate>Sun, 13 Jan 2008 20:01:18 GMT</pubDate>
<guid>http://snipplr.com/view/4546/displaying-code-snippets-wrap-long-lines-with-pre-tag/</guid>
</item>
<item>
<title>(CSS) botones que parezcan enlaces</title>
<link>http://snipplr.com/view/4545/botones-que-parezcan-enlaces/</link>
<description><![CDATA[ <p>¿Por qué empeñarnos en hacer enlaces que actúen como botones? ¿Por qué no hacemos botones que parezcan enlaces?</p> ]]></description>
<pubDate>Sun, 13 Jan 2008 19:57:42 GMT</pubDate>
<guid>http://snipplr.com/view/4545/botones-que-parezcan-enlaces/</guid>
</item>
<item>
<title>(CSS) CSS Asides in WordPress' Sandbox theme</title>
<link>http://snipplr.com/view/4237/css-asides-in-wordpress-sandbox-theme/</link>
<description><![CDATA[ <p>Implement "Asides" in a WordOress blog just with the Sandbox theme and CSS</p> ]]></description>
<pubDate>Sun, 02 Dec 2007 04:45:33 GMT</pubDate>
<guid>http://snipplr.com/view/4237/css-asides-in-wordpress-sandbox-theme/</guid>
</item>
<item>
<title>(CSS) Diagnostic stylesheet</title>
<link>http://snipplr.com/view/4234/diagnostic-stylesheet/</link>
<description><![CDATA[ <p>The primary goal here is to have a set of rules that can be applied during the development phase of a new layout. These rules’ aim is to visually highlight problems in the markup.</p> ]]></description>
<pubDate>Sat, 01 Dec 2007 15:16:01 GMT</pubDate>
<guid>http://snipplr.com/view/4234/diagnostic-stylesheet/</guid>
</item>
<item>
<title>(CSS) Master Stylesheet</title>
<link>http://snipplr.com/view/4233/master-stylesheet/</link>
<description><![CDATA[ <p>One of the most common mistakes I see beginners and intermediates fall victim to when it comes to CSS is not removing the default browser styling. This leads to inconsistencies in the appearance of your design across browsers, and ultimately leaves a lot of designers blaming the browser. It is a misplaced blame, of course. Before you do anything else when coding a website, you should reset the styling.</p> ]]></description>
<pubDate>Sat, 01 Dec 2007 15:15:09 GMT</pubDate>
<guid>http://snipplr.com/view/4233/master-stylesheet/</guid>
</item>
<item>
<title>(CSS) Técnicas CSS 3.0</title>
<link>http://snipplr.com/view/4232/tcnicas-css-30/</link>
<description><![CDATA[ <p>Si miramos al horizonte empieza a deslumbrar el futuro del CSS, con la salida de CSS3 la vida de los diseñadores web va a mejorar considerablemente y no es para menos, por que con las mejoras que se están acercando ¿quien no se aprovechará de ellas?

Echemosle un vistazo a las que parecen serán las más interesantes.</p> ]]></description>
<pubDate>Sat, 01 Dec 2007 15:05:12 GMT</pubDate>
<guid>http://snipplr.com/view/4232/tcnicas-css-30/</guid>
</item>
<item>
<title>(CSS) CSS3 Multicolumn text</title>
<link>http://snipplr.com/view/4193/css3-multicolumn-text/</link>
<description><![CDATA[ <p>The W3C multi-column module is a CSS level-three working draft, proposed by the W3C to extend the current CSS box model. The module’s intent is to allow content to flow into multiple columns inside an element. It offers new CSS properties that let the designers specify in how many columns an element should be rendered. The browser takes care of formatting the text so that the columns are balanced.

The proposed new CSS properties are:

    * ‘column-count’, to determine the number of columns into which the content of the element will flow.
    * ‘column-width’, to describe the optimal width of each column.
    * ‘column-gap’, to set the padding between columns.
    * ‘column-rule’, to define a border between columns.</p> ]]></description>
<pubDate>Sun, 25 Nov 2007 17:36:52 GMT</pubDate>
<guid>http://snipplr.com/view/4193/css3-multicolumn-text/</guid>
</item>
<item>
<title>(CSS) Transparent in all  browsers</title>
<link>http://snipplr.com/view/4192/transparent-in-all--browsers/</link>
<description><![CDATA[ <p>Transparency is one of those weird things that is treated completely differently in all browsers. To cover all your bases, you need four separate CSS statements. Fortunately they don’t interfere with each other really, so using them all every time you wish to add transparency is no big hassle and worry-free. Here they are, and are currently set to 50% transparency:
    * opacity: 0.5; This is the “most important” one because it is the current standard in CSS. This will work in most versions of Firefox, Safari, and Opera. This would be all you need if all browsers supported current standards. Which, of course, they don’t.
    * filter:alpha(opacity=50); This one you need for IE.
    * -moz-opacity:0.5; You need this one to support way old school versions of the Mozilla browsers like Netscape Navigator.
    * -khtml-opacity: 0.5; This is for way old versions of Safari (1.x) when the rendering engine it was using was still referred to as KTHML, as opposed to the current WebKit.</p> ]]></description>
<pubDate>Sun, 25 Nov 2007 17:24:48 GMT</pubDate>
<guid>http://snipplr.com/view/4192/transparent-in-all--browsers/</guid>
</item>
<item>
<title>(CSS) font-face</title>
<link>http://snipplr.com/view/4191/fontface/</link>
<description><![CDATA[ <p>Esta propiedad del CSS, que nos permite definir, en este ejemplo, la familia de fuentes “Kimberly” para luego usarla en los elementos que queramos. Esto acabará con las diferencias de visualización de página que hasta ahora dependiamos que el usuario tuviera instaladas las fuentes en su local para poder usarlas. Ahora haremos que el usuario vea la web tal y como nosotros la vemos.</p> ]]></description>
<pubDate>Sun, 25 Nov 2007 17:19:32 GMT</pubDate>
<guid>http://snipplr.com/view/4191/fontface/</guid>
</item>
<item>
<title>(CSS) Disablig deprecated HTML code</title>
<link>http://snipplr.com/view/4190/disablig-deprecated-html-code/</link>
<description><![CDATA[ <p>When handing over a project to the client, you sometimes loose control over the content HTML source. Sometimes the client uses a CMS that allows them to have full control over certain parts of the HTML, and sometimes the client simply uses your templates to insert their own HTML content in the document.
The idea is to preserve the natural cascade and inheritance in all browsers, while gracefully disabling the HTML we don’t want the client to use. That way the client will stop using it, simply because it doesn’t “work” anymore. A graceful and gentle way of guiding the client in the right direction.</p> ]]></description>
<pubDate>Sun, 25 Nov 2007 17:14:26 GMT</pubDate>
<guid>http://snipplr.com/view/4190/disablig-deprecated-html-code/</guid>
</item>
<item>
<title>(CSS) gmail-like column overflow.</title>
<link>http://snipplr.com/view/4188/gmaillike-column-overflow/</link>
<description><![CDATA[ <p>gmail-like table's column overflow.
Efecte de truncar el text en una taula si sobrepasa</p> ]]></description>
<pubDate>Sun, 25 Nov 2007 16:55:16 GMT</pubDate>
<guid>http://snipplr.com/view/4188/gmaillike-column-overflow/</guid>
</item>
<item>
<title>(CSS) Style links</title>
<link>http://snipplr.com/view/4187/style-links/</link>
<description><![CDATA[ <p>Style external links.

Inspired by: http://pooliestudios.com/projects/iconize/ and http://www.hunlock.com/blogs/Attach_icons_to_anything_with_CSS</p> ]]></description>
<pubDate>Sun, 25 Nov 2007 16:12:28 GMT</pubDate>
<guid>http://snipplr.com/view/4187/style-links/</guid>
</item>
<item>
<title>(CSS) Pullquotes</title>
<link>http://snipplr.com/view/4186/pullquotes/</link>
<description><![CDATA[ <p>Destacados (o pullquotes) en una notícia</p> ]]></description>
<pubDate>Sun, 25 Nov 2007 15:53:15 GMT</pubDate>
<guid>http://snipplr.com/view/4186/pullquotes/</guid>
</item>
</channel>
</rss>