<?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: CSS Neatness Technique</title>
	<atom:link href="http://www.nvncbl.com/2009/01/css-neatness-technique/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nvncbl.com/2009/01/css-neatness-technique/</link>
	<description>A place to log my programming solutions for future reference</description>
	<lastBuildDate>Tue, 27 Jul 2010 22:21:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: WebDragon</title>
		<link>http://www.nvncbl.com/2009/01/css-neatness-technique/comment-page-1/#comment-2098</link>
		<dc:creator>WebDragon</dc:creator>
		<pubDate>Fri, 09 Oct 2009 17:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.nvncbl.com/?p=150#comment-2098</guid>
		<description>my personal favorite trick for organizing css is done with vim&#039;s &quot;folding&quot;. You simply alter the rules for folding, for css files, and they automatically collapse down into &#039;outline format&#039;.

at the bottom of your css file you place something along the lines of 

    /* vim600: set foldenable foldmethod=marker foldmarker={,} foldlevel=1 fcl=all : */

I wrap my stylesheets inside @media all {}, or @media screen {}, etc, so this is why I have foldlevel set to 1. 

what you see as the result looks like this: 

330 +--- 10 lines: #content h2, #content h3 ----------------------
340 +---  4 lines: #content .newsitem, #content .aboutbox --------
344 +---  6 lines: #content .aboutbox #imageblock_sidebar --------
350 +---  5 lines: #content .aboutbox #imageblock_sidebar img ----

then you just scroll up and down to find the section you want, and either &#039;zo&#039; to open it, or any of the other fold-related commands

certainly makes not only scrolling around easier, but also ORGANIZING is easier because you get an overview this way.</description>
		<content:encoded><![CDATA[<p>my personal favorite trick for organizing css is done with vim&#8217;s &#8220;folding&#8221;. You simply alter the rules for folding, for css files, and they automatically collapse down into &#8216;outline format&#8217;.</p>
<p>at the bottom of your css file you place something along the lines of </p>
<p>    /* vim600: set foldenable foldmethod=marker foldmarker={,} foldlevel=1 fcl=all : */</p>
<p>I wrap my stylesheets inside @media all {}, or @media screen {}, etc, so this is why I have foldlevel set to 1. </p>
<p>what you see as the result looks like this: </p>
<p>330 +&#8212; 10 lines: #content h2, #content h3 &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-<br />
340 +&#8212;  4 lines: #content .newsitem, #content .aboutbox &#8212;&#8212;&#8211;<br />
344 +&#8212;  6 lines: #content .aboutbox #imageblock_sidebar &#8212;&#8212;&#8211;<br />
350 +&#8212;  5 lines: #content .aboutbox #imageblock_sidebar img &#8212;-</p>
<p>then you just scroll up and down to find the section you want, and either &#8216;zo&#8217; to open it, or any of the other fold-related commands</p>
<p>certainly makes not only scrolling around easier, but also ORGANIZING is easier because you get an overview this way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antonio</title>
		<link>http://www.nvncbl.com/2009/01/css-neatness-technique/comment-page-1/#comment-5</link>
		<dc:creator>Antonio</dc:creator>
		<pubDate>Tue, 06 Jan 2009 23:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.nvncbl.com/?p=150#comment-5</guid>
		<description>Good point, code collapsing would prove incredibly useful in that respect.  The only issue I can think of with that is its dependency on the IDE, which other developers may not have.  And just as a side note, I know that NuSphere&#039;s PhpED (and perhaps other IDEs) will scroll up/down in a page-up/page-down fashion when you hold down the Ctrl key and scroll.  (Just a tidbit!)</description>
		<content:encoded><![CDATA[<p>Good point, code collapsing would prove incredibly useful in that respect.  The only issue I can think of with that is its dependency on the IDE, which other developers may not have.  And just as a side note, I know that NuSphere&#8217;s PhpED (and perhaps other IDEs) will scroll up/down in a page-up/page-down fashion when you hold down the Ctrl key and scroll.  (Just a tidbit!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.nvncbl.com/2009/01/css-neatness-technique/comment-page-1/#comment-4</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Mon, 05 Jan 2009 20:12:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.nvncbl.com/?p=150#comment-4</guid>
		<description>Interesting idea.  What about using an IDE with collapsable code segments so all one sees is the signature of the element.  The problem I find is that there is just too much, indenting will definately help, but if I have fewer &quot;screens&quot; to scroll through and I can see all my elements with 1 or 2 middle-mouse scrolls, I think I&#039;d be good.</description>
		<content:encoded><![CDATA[<p>Interesting idea.  What about using an IDE with collapsable code segments so all one sees is the signature of the element.  The problem I find is that there is just too much, indenting will definately help, but if I have fewer &#8220;screens&#8221; to scroll through and I can see all my elements with 1 or 2 middle-mouse scrolls, I think I&#8217;d be good.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
