<?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: LiquidThreads visual refresh</title>
	<atom:link href="http://blog.werdn.us/2009/06/liquidthreads-visual-refresh/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.werdn.us/2009/06/liquidthreads-visual-refresh/</link>
	<description>Development, wikis and life</description>
	<lastBuildDate>Tue, 30 Mar 2010 16:44:22 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: penubag</title>
		<link>http://blog.werdn.us/2009/06/liquidthreads-visual-refresh/comment-page-1/#comment-56</link>
		<dc:creator>penubag</dc:creator>
		<pubDate>Mon, 06 Jul 2009 07:16:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.werdn.us/?p=34#comment-56</guid>
		<description>It would be great if there were an easy option for transclusion under the actions menu. 
I really dislike how half the users reply on each other&#039;s usertalk and the other half on their own and demand that their page is watched.
Is there and easy option to allow the same discussion to take place on different pages and still trigger watchlists and &quot;you have new messages&quot; template?
This is my foremost problem with our discussion system.</description>
		<content:encoded><![CDATA[<p>It would be great if there were an easy option for transclusion under the actions menu.<br />
I really dislike how half the users reply on each other&#8217;s usertalk and the other half on their own and demand that their page is watched.<br />
Is there and easy option to allow the same discussion to take place on different pages and still trigger watchlists and &#8220;you have new messages&#8221; template?<br />
This is my foremost problem with our discussion system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: penubag</title>
		<link>http://blog.werdn.us/2009/06/liquidthreads-visual-refresh/comment-page-1/#comment-45</link>
		<dc:creator>penubag</dc:creator>
		<pubDate>Fri, 03 Jul 2009 08:33:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.werdn.us/?p=34#comment-45</guid>
		<description>Can the quoted text be a grey or light color?
This will make it look less cluttered and help find the actual content.
If users have a short reply, the quoted text gets too much in the way.</description>
		<content:encoded><![CDATA[<p>Can the quoted text be a grey or light color?<br />
This will make it look less cluttered and help find the actual content.<br />
If users have a short reply, the quoted text gets too much in the way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrew</title>
		<link>http://blog.werdn.us/2009/06/liquidthreads-visual-refresh/comment-page-1/#comment-42</link>
		<dc:creator>andrew</dc:creator>
		<pubDate>Thu, 02 Jul 2009 15:36:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.werdn.us/?p=34#comment-42</guid>
		<description>I&#039;m not sure why &#039;compressing&#039; the text would be at all desirable, but it would be easily doable with CSS. I think spreading things out and adding plenty of interface around it makes people not used to wiki discussions feel more at home.

Forking threads is not presently possible, but it&#039;s an awesome idea and I&#039;ve created bug 19482 for it.

As I&#039;ve explained, there&#039;s no such thing as &#039;archiving&#039;, just being pushed off the page by newer threads. If a thread were to be forked, the two parts behave as entirely different threads, and so one part might disappear off the page faster.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure why &#8216;compressing&#8217; the text would be at all desirable, but it would be easily doable with CSS. I think spreading things out and adding plenty of interface around it makes people not used to wiki discussions feel more at home.</p>
<p>Forking threads is not presently possible, but it&#8217;s an awesome idea and I&#8217;ve created bug 19482 for it.</p>
<p>As I&#8217;ve explained, there&#8217;s no such thing as &#8216;archiving&#8217;, just being pushed off the page by newer threads. If a thread were to be forked, the two parts behave as entirely different threads, and so one part might disappear off the page faster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: siebrand</title>
		<link>http://blog.werdn.us/2009/06/liquidthreads-visual-refresh/comment-page-1/#comment-37</link>
		<dc:creator>siebrand</dc:creator>
		<pubDate>Tue, 30 Jun 2009 21:09:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.werdn.us/?p=34#comment-37</guid>
		<description>I&#039;ve seen you do a lot of work on this. Threaded discussions are potentially a huge usability improvement for discussion when using MediaWiki, especially for those with less experience in wiki editing.

What I like about how we discuss things currently on talk pages is that the threads are nicely &#039;compressed&#039;. There is little space between replies and topics.

Your screenshot still shows a lot of whitespace. Would there be a way to compress the current interface (further)? It looks to me like especially the &#039;reply&#039; line is taking up a lot of space, but you might have some reason to have done it like this...</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen you do a lot of work on this. Threaded discussions are potentially a huge usability improvement for discussion when using MediaWiki, especially for those with less experience in wiki editing.</p>
<p>What I like about how we discuss things currently on talk pages is that the threads are nicely &#8216;compressed&#8217;. There is little space between replies and topics.</p>
<p>Your screenshot still shows a lot of whitespace. Would there be a way to compress the current interface (further)? It looks to me like especially the &#8216;reply&#8217; line is taking up a lot of space, but you might have some reason to have done it like this&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike.lifeguard</title>
		<link>http://blog.werdn.us/2009/06/liquidthreads-visual-refresh/comment-page-1/#comment-35</link>
		<dc:creator>Mike.lifeguard</dc:creator>
		<pubDate>Tue, 30 Jun 2009 15:18:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.werdn.us/?p=34#comment-35</guid>
		<description>The ten threads per page limit needs to be configurable on a per-page basis.

Is there any mechanism to fork threads?

Is there any way to archive only part of a thread?</description>
		<content:encoded><![CDATA[<p>The ten threads per page limit needs to be configurable on a per-page basis.</p>
<p>Is there any mechanism to fork threads?</p>
<p>Is there any way to archive only part of a thread?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
