<?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 for Tim Babych’s thoughts</title>
	<atom:link href="http://blog.clear.com.ua/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.clear.com.ua</link>
	<description>Thoughts on web, things and so on</description>
	<lastBuildDate>Thu, 01 Sep 2011 07:07:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Teh magic by Tim Babych</title>
		<link>http://blog.clear.com.ua/2011/08/bz-import/comment-page-1/#comment-3694</link>
		<dc:creator>Tim Babych</dc:creator>
		<pubDate>Thu, 01 Sep 2011 07:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.clear.com.ua/?p=130#comment-3694</guid>
		<description>&lt;p&gt;&lt;pre&gt;&lt;code&gt;                    You simply start a new test project as a regular user now. Just note that at the moment only plain directory structures like LANG/files are supported.
&lt;/code&gt;&lt;/pre&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><pre><code>                    You simply start a new test project as a regular user now. Just note that at the moment only plain directory structures like LANG/files are supported.
</code></pre></p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Teh magic by Tim Babych</title>
		<link>http://blog.clear.com.ua/2011/08/bz-import/comment-page-1/#comment-3693</link>
		<dc:creator>Tim Babych</dc:creator>
		<pubDate>Thu, 01 Sep 2011 07:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.clear.com.ua/?p=130#comment-3693</guid>
		<description>&lt;p&gt;You simply start a new project as a regular user now.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You simply start a new project as a regular user now.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Teh magic by Goofy</title>
		<link>http://blog.clear.com.ua/2011/08/bz-import/comment-page-1/#comment-3692</link>
		<dc:creator>Goofy</dc:creator>
		<pubDate>Thu, 01 Sep 2011 07:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.clear.com.ua/?p=130#comment-3692</guid>
		<description>&lt;p&gt;mmh can&#039;t test it atm editor/editor is not working&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>mmh can&#8217;t test it atm editor/editor is not working</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on CleverCSS by Massimiliano Torromeo</title>
		<link>http://blog.clear.com.ua/2009/09/clevercss/comment-page-1/#comment-1801</link>
		<dc:creator>Massimiliano Torromeo</dc:creator>
		<pubDate>Fri, 30 Apr 2010 18:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.clear.com.ua/?p=68#comment-1801</guid>
		<description>&lt;p&gt;Hi,
I tried CleverCSS recently but I encountered several issues with it&#039;s parser engine like the problem you described with margin: -2px -2px, or trying some vendor rules like -webkit-gradient(). The developer definetly got carried away with features.&lt;/p&gt;

&lt;p&gt;That&#039;s why I wrote CleanCSS. Same indentation-based syntax, without all those functionalities that added to much complexity to a great idea.&lt;/p&gt;

&lt;p&gt;I also figured I would not implement CSS variables since I find it works great if you preprocess the ccss with a templating engine like mako or jinja if you really need them.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi,
I tried CleverCSS recently but I encountered several issues with it&#8217;s parser engine like the problem you described with margin: -2px -2px, or trying some vendor rules like -webkit-gradient(). The developer definetly got carried away with features.</p>

<p>That&#8217;s why I wrote CleanCSS. Same indentation-based syntax, without all those functionalities that added to much complexity to a great idea.</p>

<p>I also figured I would not implement CSS variables since I find it works great if you preprocess the ccss with a templating engine like mako or jinja if you really need them.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on CleverCSS by Peter Pöml</title>
		<link>http://blog.clear.com.ua/2009/09/clevercss/comment-page-1/#comment-1155</link>
		<dc:creator>Peter Pöml</dc:creator>
		<pubDate>Thu, 25 Mar 2010 20:33:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.clear.com.ua/?p=68#comment-1155</guid>
		<description>&lt;p&gt;Sorry, the line breaks were hosed when I pasted the patch. I put it here as a file:
http://www.poeml.de/users/poeml/python-clevercss-poeml-comments.patch&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sorry, the line breaks were hosed when I pasted the patch. I put it here as a file:
<a href="http://www.poeml.de/users/poeml/python-clevercss-poeml-comments.patch" rel="nofollow">http://www.poeml.de/users/poeml/python-clevercss-poeml-comments.patch</a></p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on CleverCSS by Peter Pöml</title>
		<link>http://blog.clear.com.ua/2009/09/clevercss/comment-page-1/#comment-1127</link>
		<dc:creator>Peter Pöml</dc:creator>
		<pubDate>Wed, 24 Mar 2010 18:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.clear.com.ua/?p=68#comment-1127</guid>
		<description>&lt;p&gt;Hi Tim,&lt;/p&gt;

&lt;p&gt;could you please integrate the following patch in your tree? It fixes a small shortcoming that itched me quite a bit today.&lt;/p&gt;

&lt;p&gt;Thanks!
Peter&lt;/p&gt;

&lt;p&gt;% cat python-clevercss-poeml-comments.patch
handle whitespace in front of comments
poeml, Wed Mar 24 19:01:31 CET 2010&lt;/p&gt;

&lt;p&gt;Index: dziegler-clevercss-2272da5785fd9a5a723ea12a5d7081bec20b7c9b/clevercss.py&lt;/p&gt;

&lt;p&gt;--- dziegler-clevercss-2272da5785fd9a5a723ea12a5d7081bec20b7c9b.orig/clevercss.py
+++ dziegler-clevercss-2272da5785fd9a5a723ea12a5d7081bec20b7c9b/clevercss.py
@@ -541,6 +541,9 @@ class LineIterator(object):
             return self.lineno, line&lt;/p&gt;

&lt;p&gt;&lt;pre&gt;&lt;code&gt;     stripped_line = line[:comment_start]
&lt;/code&gt;&lt;/pre&gt;&lt;/p&gt;

&lt;p&gt;+        # ignore also comments that have leading space;
+        # stripping from the right makes sure that the line is empty otherwise:
+        stripped_line = stripped_line.rstrip()
         comment_end = line.find(&#039;*/&#039;, comment_start)
         if comment_end &gt;= 0:
             return self.lineno, stripped_line + line[comment_end + 2:]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi Tim,</p>

<p>could you please integrate the following patch in your tree? It fixes a small shortcoming that itched me quite a bit today.</p>

<p>Thanks!
Peter</p>

<p>% cat python-clevercss-poeml-comments.patch
handle whitespace in front of comments
poeml, Wed Mar 24 19:01:31 CET 2010</p>

<p>Index: dziegler-clevercss-2272da5785fd9a5a723ea12a5d7081bec20b7c9b/clevercss.py</p>

<p>&#8212; dziegler-clevercss-2272da5785fd9a5a723ea12a5d7081bec20b7c9b.orig/clevercss.py
+++ dziegler-clevercss-2272da5785fd9a5a723ea12a5d7081bec20b7c9b/clevercss.py
@@ -541,6 +541,9 @@ class LineIterator(object):
             return self.lineno, line</p>

<p><pre><code>     stripped_line = line[:comment_start]
</code></pre></p>

<p>+        # ignore also comments that have leading space;
+        # stripping from the right makes sure that the line is empty otherwise:
+        stripped_line = stripped_line.rstrip()
         comment_end = line.find(&#8216;*/&#8217;, comment_start)
         if comment_end &gt;= 0:
             return self.lineno, stripped_line + line[comment_end + 2:]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Rebuilding the friendship between Firefox and eBooks by aladinus</title>
		<link>http://blog.clear.com.ua/2009/09/firefox-and-ebooks/comment-page-1/#comment-746</link>
		<dc:creator>aladinus</dc:creator>
		<pubDate>Fri, 29 Jan 2010 21:58:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.clear.com.ua/?p=23#comment-746</guid>
		<description>&lt;p&gt;Please make support for smooth scrolling with add-on  SmoothWheel (https://addons.mozilla.org/en-US/firefox/addon/357) or Yet Another Smooth Scrolling (https://addons.mozilla.org/en-US/firefox/addon/5846)&lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Please make support for smooth scrolling with add-on  SmoothWheel (<a href="https://addons.mozilla.org/en-US/firefox/addon/357" rel="nofollow">https://addons.mozilla.org/en-US/firefox/addon/357</a>) or Yet Another Smooth Scrolling (<a href="https://addons.mozilla.org/en-US/firefox/addon/5846" rel="nofollow">https://addons.mozilla.org/en-US/firefox/addon/5846</a>)</p>

<p>Thanks!</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Rebuilding the friendship between Firefox and eBooks by skierpage</title>
		<link>http://blog.clear.com.ua/2009/09/firefox-and-ebooks/comment-page-1/#comment-40</link>
		<dc:creator>skierpage</dc:creator>
		<pubDate>Thu, 01 Oct 2009 04:03:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.clear.com.ua/?p=23#comment-40</guid>
		<description>&lt;p&gt;Yes please.&lt;/p&gt;

&lt;p&gt;You may not have to unzip the content.  Firefox implements Sun&#039;s jar: protocol, so it can view jar:file:///path/to/my/ebook.fb2!/chapter2.html .&lt;/p&gt;

&lt;p&gt;Two features I&#039;ve always wanted when reading Gutenberg books in a browser are a) a bookmark, and b) &quot;Search from beginning to here but no further&quot;.  Otherwise you search for &quot;Dumbledore&quot; and -&gt;Next scrolls you to the page at the end where he dies, d&#039;oh.&lt;/p&gt;

&lt;p&gt;Good luck.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Yes please.</p>

<p>You may not have to unzip the content.  Firefox implements Sun&#8217;s jar: protocol, so it can view jar:file:///path/to/my/ebook.fb2!/chapter2.html .</p>

<p>Two features I&#8217;ve always wanted when reading Gutenberg books in a browser are a) a bookmark, and b) &#8220;Search from beginning to here but no further&#8221;.  Otherwise you search for &#8220;Dumbledore&#8221; and -&gt;Next scrolls you to the page at the end where he dies, d&#8217;oh.</p>

<p>Good luck.</p>]]></content:encoded>
	</item>
</channel>
</rss>

