<?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: Onfolio 2.0 revisited</title>
	<atom:link href="http://blog.brentc.com/2005/02/onfolio-20-revisited/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.brentc.com/2005/02/onfolio-20-revisited/</link>
	<description>Random Babblings</description>
	<lastBuildDate>Sat, 19 Sep 2009 17:00:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.brentc.com/2005/02/onfolio-20-revisited/comment-page-1/#comment-69</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 19 Feb 2005 12:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://wp.apathyant.com/2005/02/onfolio-20-revisited/#comment-69</guid>
		<description>FYI for final release we are going to fix the P / BLOCKQUOTE spacing issue as well as add an option to post only a summary of feed items for link-blogging. Alas the character set issues you identified are a result of Blogger not handling non-ASCII characters (I would imagine this will be fixed by them in the not too distant future).</description>
		<content:encoded><![CDATA[<p>FYI for final release we are going to fix the P / BLOCKQUOTE spacing issue as well as add an option to post only a summary of feed items for link-blogging. Alas the character set issues you identified are a result of Blogger not handling non-ASCII characters (I would imagine this will be fixed by them in the not too distant future).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brent</title>
		<link>http://blog.brentc.com/2005/02/onfolio-20-revisited/comment-page-1/#comment-68</link>
		<dc:creator>brent</dc:creator>
		<pubDate>Thu, 17 Feb 2005 03:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://wp.apathyant.com/2005/02/onfolio-20-revisited/#comment-68</guid>
		<description>Mike: It&#039;s neat to know that someone&#039;s actually listening.</description>
		<content:encoded><![CDATA[<p>Mike: It&#8217;s neat to know that someone&#8217;s actually listening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brent</title>
		<link>http://blog.brentc.com/2005/02/onfolio-20-revisited/comment-page-1/#comment-67</link>
		<dc:creator>brent</dc:creator>
		<pubDate>Thu, 17 Feb 2005 03:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://wp.apathyant.com/2005/02/onfolio-20-revisited/#comment-67</guid>
		<description>Spike: I&#039;ll try out the css...&lt;br /&gt;You know, I thought there might be a way to get some of the functionality through editing a css file, but I never actually looked to see what was in the onfolio directory.&lt;br /&gt;&lt;br /&gt;Thanks.</description>
		<content:encoded><![CDATA[<p>Spike: I&#8217;ll try out the css&#8230;<br />You know, I thought there might be a way to get some of the functionality through editing a css file, but I never actually looked to see what was in the onfolio directory.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spike Washburn</title>
		<link>http://blog.brentc.com/2005/02/onfolio-20-revisited/comment-page-1/#comment-66</link>
		<dc:creator>Spike Washburn</dc:creator>
		<pubDate>Thu, 17 Feb 2005 02:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://wp.apathyant.com/2005/02/onfolio-20-revisited/#comment-66</guid>
		<description>Wow, thanks for the detailed comments.  This kind of feedback really helps us make the product better.&lt;br /&gt;&lt;br /&gt;The problem with posting unicode characters is unfortunately a documented bug in the Blogger posting APIs.  Until Blogger fixes the issue, no tools are able to post non-ASCII characters into their system.  Onfolio is able to post Unicode content into other services (like Typepad).&lt;br /&gt;&lt;br /&gt;You might be able to get the newspaper collapsing behavior you want by tweaking the newspaper stylesheet to make it collapse read items.  If you add the following CSS rules to the bottom of the Onfolio/HtmlWorkspace/newspaper.css file, the items you have read will display collapsed.&lt;br /&gt;&lt;br /&gt;------ Collapse read items CSS -----&lt;br /&gt;.item-selected .item-content, .item-selected .publish-time, .item-selected .feed-home{ display: block; }&lt;br /&gt;.item-read&lt;br /&gt;{&lt;br /&gt; padding-bottom: 0em;&lt;br /&gt; margin-top: 0em;&lt;br /&gt; margin-bottom: 0em;&lt;br /&gt; border-bottom: 1px solid #D3D3D3;&lt;br /&gt; padding-left: .5em;&lt;br /&gt; padding-right: .5em;&lt;br /&gt; /*font-size: .8em;*/&lt;br /&gt;}&lt;br /&gt;.item-read .item-content, .item-read .publish-time, .item-read .feed-home&lt;br /&gt;{&lt;br /&gt; display: none;&lt;br /&gt;}</description>
		<content:encoded><![CDATA[<p>Wow, thanks for the detailed comments.  This kind of feedback really helps us make the product better.</p>
<p>The problem with posting unicode characters is unfortunately a documented bug in the Blogger posting APIs.  Until Blogger fixes the issue, no tools are able to post non-ASCII characters into their system.  Onfolio is able to post Unicode content into other services (like Typepad).</p>
<p>You might be able to get the newspaper collapsing behavior you want by tweaking the newspaper stylesheet to make it collapse read items.  If you add the following CSS rules to the bottom of the Onfolio/HtmlWorkspace/newspaper.css file, the items you have read will display collapsed.</p>
<p>&#8212;&#8212; Collapse read items CSS &#8212;&#8211;<br />.item-selected .item-content, .item-selected .publish-time, .item-selected .feed-home{ display: block; }<br />.item-read<br />{<br /> padding-bottom: 0em;<br /> margin-top: 0em;<br /> margin-bottom: 0em;<br /> border-bottom: 1px solid #D3D3D3;<br /> padding-left: .5em;<br /> padding-right: .5em;<br /> /*font-size: .8em;*/<br />}<br />.item-read .item-content, .item-read .publish-time, .item-read .feed-home<br />{<br /> display: none;<br />}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://blog.brentc.com/2005/02/onfolio-20-revisited/comment-page-1/#comment-65</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 16 Feb 2005 22:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://wp.apathyant.com/2005/02/onfolio-20-revisited/#comment-65</guid>
		<description>Thanks for the great feedback.  I am on the QA team over at Onfolio and just wanted to let you know that I have entered defects and feature requests into our tracking systems for following up on.  &lt;br /&gt;I will tell you that we have talked about some of the feeds feedback internally in the past already, so those are definately some good ideas.  The pagination request is something one of the feeds developers likes as well.  There&#039;s always more tweaks/polishing that can be added to a product.  2.0 is buttoned up pretty tight for now, but look for some of these features in a future release.  &lt;br /&gt;I&#039;m looking into the charset issue because it does not seem to always occur, even within blogger accounts, but we&#039;ll track it down and see what we can do about it.&lt;br /&gt;Thanks again for the great feedback.</description>
		<content:encoded><![CDATA[<p>Thanks for the great feedback.  I am on the QA team over at Onfolio and just wanted to let you know that I have entered defects and feature requests into our tracking systems for following up on.  <br />I will tell you that we have talked about some of the feeds feedback internally in the past already, so those are definately some good ideas.  The pagination request is something one of the feeds developers likes as well.  There&#8217;s always more tweaks/polishing that can be added to a product.  2.0 is buttoned up pretty tight for now, but look for some of these features in a future release.  <br />I&#8217;m looking into the charset issue because it does not seem to always occur, even within blogger accounts, but we&#8217;ll track it down and see what we can do about it.<br />Thanks again for the great feedback.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
