<?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 visophyte: shiny? shiny.</title>
	<atom:link href="http://www.visophyte.org/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.visophyte.org/blog</link>
	<description>Andrew Sutherland writes things but (almost) always includes pictures to look at.</description>
	<lastBuildDate>Wed, 08 Sep 2010 01:17:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Documentation for complex things (you don&#8217;t basically already understand) by skierpage</title>
		<link>http://www.visophyte.org/blog/2010/09/07/documentation-for-complex-things-you-dont-basically-already-understand/comment-page-1/#comment-3720</link>
		<dc:creator>skierpage</dc:creator>
		<pubDate>Wed, 08 Sep 2010 01:17:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=562#comment-3720</guid>
		<description>That&#039;s amazing!  Please show it to the MDN folks because the MDC could really use something similar.  It&#039;s frustrating when the code snippets for an interactive read-write web are non-interactive and uneditable.

I take it the [Boilerplate] and [Example Insertion] expanding boxes are the rest of the complete code sample?   That&#039;s great, if a bit unclear at first. I assumed clicking on the code snippet would have to open the entire sample program and the author would just hope the reader finds the appropriate section to play with.</description>
		<content:encoded><![CDATA[<p>That&#8217;s amazing!  Please show it to the MDN folks because the MDC could really use something similar.  It&#8217;s frustrating when the code snippets for an interactive read-write web are non-interactive and uneditable.</p>
<p>I take it the [Boilerplate] and [Example Insertion] expanding boxes are the rest of the complete code sample?   That&#8217;s great, if a bit unclear at first. I assumed clicking on the code snippet would have to open the entire sample program and the author would just hope the reader finds the appropriate section to play with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on (clicky.visophyte.org-hosted CouchDB services offline) by Andrew Sutherland</title>
		<link>http://www.visophyte.org/blog/2010/08/08/clicky-visophyte-org-hosted-couchdb-services-offline/comment-page-1/#comment-3495</link>
		<dc:creator>Andrew Sutherland</dc:creator>
		<pubDate>Mon, 09 Aug 2010 20:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=552#comment-3495</guid>
		<description>I had not seen PyDocWeb.  It looks very nice.  Python has been in a pretty good place from a documentation perspective for quite some time, and a web-editor front-end is just icing on the delicious cake!

The &quot;something better&quot; is more about a system for tutorial-style documentation with inline examples that are executed and can be edited and re-executed within the page.  The motivating factor for my documentation is basically Jetpack for Thunderbird.  The APIs are complex enough that a docstring REPL call-and-answer is insufficient to demonstrate the APIs successfully so it&#039;s important to be able to embed HTML results in the document and nice to be able to intelligently hyperlink the JS source to the appropriate documentation.

After having re-surveyed the existing JS documentation field, the main alternative to &quot;roll your own&quot; was to use the approach being used by the Jetpack team, but they do not have a solution for the interactive/editable examples at this time.

Reference documentation is still important to me and my solution is able to do such things and will be able to interoperate, but I have no goal at world domination on that front.</description>
		<content:encoded><![CDATA[<p>I had not seen PyDocWeb.  It looks very nice.  Python has been in a pretty good place from a documentation perspective for quite some time, and a web-editor front-end is just icing on the delicious cake!</p>
<p>The &#8220;something better&#8221; is more about a system for tutorial-style documentation with inline examples that are executed and can be edited and re-executed within the page.  The motivating factor for my documentation is basically Jetpack for Thunderbird.  The APIs are complex enough that a docstring REPL call-and-answer is insufficient to demonstrate the APIs successfully so it&#8217;s important to be able to embed HTML results in the document and nice to be able to intelligently hyperlink the JS source to the appropriate documentation.</p>
<p>After having re-surveyed the existing JS documentation field, the main alternative to &#8220;roll your own&#8221; was to use the approach being used by the Jetpack team, but they do not have a solution for the interactive/editable examples at this time.</p>
<p>Reference documentation is still important to me and my solution is able to do such things and will be able to interoperate, but I have no goal at world domination on that front.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on (clicky.visophyte.org-hosted CouchDB services offline) by Janet Swisher</title>
		<link>http://www.visophyte.org/blog/2010/08/08/clicky-visophyte-org-hosted-couchdb-services-offline/comment-page-1/#comment-3494</link>
		<dc:creator>Janet Swisher</dc:creator>
		<pubDate>Mon, 09 Aug 2010 16:57:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=552#comment-3494</guid>
		<description>This is the first time I&#039;ve heard of doccelerator, so I&#039;m eager to to hear more about the &quot;something better&quot; that&#039;s coming. Regarding the &quot;round-trip doc comments from the wiki&quot; strategy, have you see PyDocWeb for Python? (http://code.google.com/p/pydocweb/)</description>
		<content:encoded><![CDATA[<p>This is the first time I&#8217;ve heard of doccelerator, so I&#8217;m eager to to hear more about the &#8220;something better&#8221; that&#8217;s coming. Regarding the &#8220;round-trip doc comments from the wiki&#8221; strategy, have you see PyDocWeb for Python? (<a href="http://code.google.com/p/pydocweb/" rel="nofollow">http://code.google.com/p/pydocweb/</a>)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Thunderbird Quick Filter Bar extensions, they&#8217;re a thing! by Andrew Sutherland</title>
		<link>http://www.visophyte.org/blog/2010/05/02/thunderbird-quick-filter-bar-extensions-theyre-a-thing/comment-page-1/#comment-3488</link>
		<dc:creator>Andrew Sutherland</dc:creator>
		<pubDate>Mon, 09 Aug 2010 06:06:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=519#comment-3488</guid>
		<description>It wouldn&#039;t be hard to do, but you might be better served by &quot;show in conversation&quot; in the &quot;other actions&quot; drop-down menu accessible from the message reader.</description>
		<content:encoded><![CDATA[<p>It wouldn&#8217;t be hard to do, but you might be better served by &#8220;show in conversation&#8221; in the &#8220;other actions&#8221; drop-down menu accessible from the message reader.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Thunderbird Quick Filter Bar extensions, they&#8217;re a thing! by Christian</title>
		<link>http://www.visophyte.org/blog/2010/05/02/thunderbird-quick-filter-bar-extensions-theyre-a-thing/comment-page-1/#comment-3482</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Tue, 27 Jul 2010 07:23:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=519#comment-3482</guid>
		<description>Excellent, 

would it be possible to filter by same subject ? I tried to look at the code, but I&#039;m a little bit confused.</description>
		<content:encoded><![CDATA[<p>Excellent, </p>
<p>would it be possible to filter by same subject ? I tried to look at the code, but I&#8217;m a little bit confused.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ediosk: an emacs buffer switcher for the rest of us by Ted Mielczarek</title>
		<link>http://www.visophyte.org/blog/2010/07/24/ediosk-an-emacs-buffer-switcher-for-the-rest-of-us/comment-page-1/#comment-3465</link>
		<dc:creator>Ted Mielczarek</dc:creator>
		<pubDate>Sun, 25 Jul 2010 01:10:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=543#comment-3465</guid>
		<description>Sounds like a good start toward &quot;Buffer Candy&quot;.</description>
		<content:encoded><![CDATA[<p>Sounds like a good start toward &#8220;Buffer Candy&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on understanding where layout goes wrong with gecko reflow debug logs (Part 1) by Andrew Sutherland</title>
		<link>http://www.visophyte.org/blog/2010/07/03/understanding-where-layout-goes-wrong-with-gecko-reflow-debug-logs-part-1/comment-page-1/#comment-3426</link>
		<dc:creator>Andrew Sutherland</dc:creator>
		<pubDate>Sun, 04 Jul 2010 13:56:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=531#comment-3426</guid>
		<description>Not XUL! HTML!

In the off-chance someone with deep layout experience (you?) would take a look, it is most useful to me to know what pieces of information they would want/need that the raw reflow debugging log provides but the summary does not, or that the raw reflow log does not provide but could.  So I&#039;ve biased in that direction...</description>
		<content:encoded><![CDATA[<p>Not XUL! HTML!</p>
<p>In the off-chance someone with deep layout experience (you?) would take a look, it is most useful to me to know what pieces of information they would want/need that the raw reflow debugging log provides but the summary does not, or that the raw reflow log does not provide but could.  So I&#8217;ve biased in that direction&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on understanding where layout goes wrong with gecko reflow debug logs (Part 1) by Neil Rashbrook</title>
		<link>http://www.visophyte.org/blog/2010/07/03/understanding-where-layout-goes-wrong-with-gecko-reflow-debug-logs-part-1/comment-page-1/#comment-3425</link>
		<dc:creator>Neil Rashbrook</dc:creator>
		<pubDate>Sun, 04 Jul 2010 10:25:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=531#comment-3425</guid>
		<description>So what does the actual XUL source look like?</description>
		<content:encoded><![CDATA[<p>So what does the actual XUL source look like?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Thunderbird Quick Filter Bar extensions, they&#8217;re a thing! by Andrew Sutherland</title>
		<link>http://www.visophyte.org/blog/2010/05/02/thunderbird-quick-filter-bar-extensions-theyre-a-thing/comment-page-1/#comment-3423</link>
		<dc:creator>Andrew Sutherland</dc:creator>
		<pubDate>Fri, 18 Jun 2010 19:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=519#comment-3423</guid>
		<description>Yes, someone could write an extension that does that and be able to reuse most of the work that went into the quick filter bar.</description>
		<content:encoded><![CDATA[<p>Yes, someone could write an extension that does that and be able to reuse most of the work that went into the quick filter bar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Thunderbird Quick Filter Bar extensions, they&#8217;re a thing! by Charles</title>
		<link>http://www.visophyte.org/blog/2010/05/02/thunderbird-quick-filter-bar-extensions-theyre-a-thing/comment-page-1/#comment-3422</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Fri, 18 Jun 2010 18:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.visophyte.org/blog/?p=519#comment-3422</guid>
		<description>Hi Andrew,

I&#039;m a little dismayed at the conversion of a small searchbox (the old quickfilter search box) that could be placed on any toolbar desired, into a huge new toolbar that cannot be modified in any way.

I do see the argument, and like some of the new features (the ability to create your own combinations of criteria), but I have a question...

Is this coded in such a way that the old quickfilter searchbox could be brought back but with some of the new features?

What I&#039;d like is the old searchbox (I place everything on my menu bar, then use the Autohide extension to auto-hide/show it on mouse-over, just like the Windows Taskbar), but with the nice little Sticky pin added immediately to the left, and a new &#039;select/drop-down&#039; menu for selecting the individual criteria - ie, you click in the drop-down, start clicking on the criteria until you get the ones you want enabled/disabled, then click off the menu and it applies your changes.</description>
		<content:encoded><![CDATA[<p>Hi Andrew,</p>
<p>I&#8217;m a little dismayed at the conversion of a small searchbox (the old quickfilter search box) that could be placed on any toolbar desired, into a huge new toolbar that cannot be modified in any way.</p>
<p>I do see the argument, and like some of the new features (the ability to create your own combinations of criteria), but I have a question&#8230;</p>
<p>Is this coded in such a way that the old quickfilter searchbox could be brought back but with some of the new features?</p>
<p>What I&#8217;d like is the old searchbox (I place everything on my menu bar, then use the Autohide extension to auto-hide/show it on mouse-over, just like the Windows Taskbar), but with the nice little Sticky pin added immediately to the left, and a new &#8216;select/drop-down&#8217; menu for selecting the individual criteria &#8211; ie, you click in the drop-down, start clicking on the criteria until you get the ones you want enabled/disabled, then click off the menu and it applies your changes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
