<?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: Once More, With Flavor!</title>
	<atom:link href="http://nslog.com/2004/05/11/once_more_with_flavor/feed" rel="self" type="application/rss+xml" />
	<link>http://nslog.com/2004/05/11/once_more_with_flavor</link>
	<description>The Weblog of Erik J. Barzeski</description>
	<lastBuildDate>Wed, 23 May 2012 23:05:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Greg Pfeil</title>
		<link>http://nslog.com/2004/05/11/once_more_with_flavor#comment-9163</link>
		<dc:creator>Greg Pfeil</dc:creator>
		<pubDate>Wed, 12 May 2004 19:26:55 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2004/05/11/once_more_with_flavor/#comment-9163</guid>
		<description>As far as the per-feed stylesheet is concerned, why not just have the feed publisher use the &quot;xml-stylesheet&quot; processing instruction. It requires no change to any feed spec, is easy to parse correctly, and is an official W3C Recommendation.



http://www.w3.org/TR/xml-stylesheet/



As far as dealing with ugly ones, the user should be able to set a single custom stylesheet in PF. Then, should have the option to &quot;turn-off&quot; the publisher&#039;s stylesheet in any given feed, which will then fall back to the user&#039;s cusom sheet (or the default if no custom was set). It seems like the toggle for this should have a keyboard shortcut to toggle the current feed -- maybe cmd-opt-S or something?



Maybe also have a global &quot;Use publisher&#039;s style sheet if provided&quot; preference that defaults to &quot;on&quot;.



I wish I could play with this myself :P Waiting not-so-patiently over here.
</description>
		<content:encoded><![CDATA[<p>As far as the per-feed stylesheet is concerned, why not just have the feed publisher use the "xml-stylesheet" processing instruction. It requires no change to any feed spec, is easy to parse correctly, and is an official W3C Recommendation.</p>
<p><a  href="http://www.w3.org/TR/xml-stylesheet/">http://www.w3.org/TR/xml-stylesheet/</a></p>
<p>As far as dealing with ugly ones, the user should be able to set a single custom stylesheet in PF. Then, should have the option to "turn-off" the publisher's stylesheet in any given feed, which will then fall back to the user's cusom sheet (or the default if no custom was set). It seems like the toggle for this should have a keyboard shortcut to toggle the current feed -- maybe cmd-opt-S or something?</p>
<p>Maybe also have a global "Use publisher's style sheet if provided" preference that defaults to "on".</p>
<p>I wish I could play with this myself <img src='http://nslog.com/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' />  Waiting not-so-patiently over here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arcterex</title>
		<link>http://nslog.com/2004/05/11/once_more_with_flavor#comment-9162</link>
		<dc:creator>Arcterex</dc:creator>
		<pubDate>Wed, 12 May 2004 16:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2004/05/11/once_more_with_flavor/#comment-9162</guid>
		<description>I don&#039;t think it&#039;s an issue of 1 feed per folder (which is silly IMHO), but it&#039;s the ability to organize into other folders.  If you read 500 feeds a day you probably want a little bit of organization, such as &#039;friends&#039;, &#039;work&#039;, &#039;news&#039;, &#039;other-interesting&#039;, &#039;other-boring&#039; and so on.  



What I wanted to see was the ability to easily set up those 500 feeds (imported from wherever) into those 5 or 10 different categories so that when you read them and when you search their content, you have a little more context to what you are doing.   The filtering system in PF is very good, but there are some things (ie: drag feed to a folder and have it autmagically be added to that folder via filterize) which would make this organization even better.  



You aren&#039;t going to use the app the same way as me, or $otherdude, or $otherotherdude.  Best thing you can do is identify the &quot;core sets&quot; of uses that go on and ensure the app works well for most major cases.  And I think that PF is well on it&#039;s way, or at least, to satisfy my uses :)



The other in-escapable fact is that NNW is the defacto standard right now (IMHO) and most people grew up on doing RSS that way, so they are used to it.</description>
		<content:encoded><![CDATA[<p>I don't think it's an issue of 1 feed per folder (which is silly IMHO), but it's the ability to organize into other folders.  If you read 500 feeds a day you probably want a little bit of organization, such as 'friends', 'work', 'news', 'other-interesting', 'other-boring' and so on.  </p>
<p>What I wanted to see was the ability to easily set up those 500 feeds (imported from wherever) into those 5 or 10 different categories so that when you read them and when you search their content, you have a little more context to what you are doing.   The filtering system in PF is very good, but there are some things (ie: drag feed to a folder and have it autmagically be added to that folder via filterize) which would make this organization even better.  </p>
<p>You aren't going to use the app the same way as me, or $otherdude, or $otherotherdude.  Best thing you can do is identify the "core sets" of uses that go on and ensure the app works well for most major cases.  And I think that PF is well on it's way, or at least, to satisfy my uses <img src='http://nslog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>The other in-escapable fact is that NNW is the defacto standard right now (IMHO) and most people grew up on doing RSS that way, so they are used to it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caleb Jaffa</title>
		<link>http://nslog.com/2004/05/11/once_more_with_flavor#comment-9161</link>
		<dc:creator>Caleb Jaffa</dc:creator>
		<pubDate>Wed, 12 May 2004 15:35:54 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2004/05/11/once_more_with_flavor/#comment-9161</guid>
		<description>Yeah, thanks for having space shift not work as expected, now I know what to expect when I press it.</description>
		<content:encoded><![CDATA[<p>Yeah, thanks for having space shift not work as expected, now I know what to expect when I press it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Burkhardt</title>
		<link>http://nslog.com/2004/05/11/once_more_with_flavor#comment-9160</link>
		<dc:creator>Chris Burkhardt</dc:creator>
		<pubDate>Tue, 11 May 2004 23:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2004/05/11/once_more_with_flavor/#comment-9160</guid>
		<description>Woah, I was never aware that shift-space did anything. Cool.</description>
		<content:encoded><![CDATA[<p>Woah, I was never aware that shift-space did anything. Cool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Clark</title>
		<link>http://nslog.com/2004/05/11/once_more_with_flavor#comment-9159</link>
		<dc:creator>Chris Clark</dc:creator>
		<pubDate>Tue, 11 May 2004 23:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2004/05/11/once_more_with_flavor/#comment-9159</guid>
		<description>Excellent... [tents fingers]</description>
		<content:encoded><![CDATA[<p>Excellent... [tents fingers]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

