<?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: Writeboard: Class projects reinvented</title>
	<atom:link href="http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/feed/" rel="self" type="application/rss+xml" />
	<link>http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/</link>
	<description>tech, simplified.</description>
	<lastBuildDate>Wed, 16 May 2012 03:53:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Henk Kleynhans</title>
		<link>http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/comment-page-1/#comment-40</link>
		<dc:creator>Henk Kleynhans</dc:creator>
		<pubDate>Sun, 31 Jan 2010 23:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/#comment-40</guid>
		<description>Hi Matthew, I stopped using Writeboards the moment we were able to use Google Docs. (and now use Google Sites for project documentation). 

The problem with Writeboards is that the process is all wrong:

1. View (assuming it&#039;s an existing document

2. Click Edit, to edit a paragraph

3. Wait for the editor to load

4. Scroll down &amp; Squint in order to find the paragraph that you wanted to edit. (let&#039;s say you want to insert a small table, for which you&#039;ll need to know HTML)

5. Click &#039;Save as newest version&#039; and wait again to see latest version. 

6. Oops! You forgot a closing  somewhere! (or to bold a word, or a numbered list looks wrong)

7. Click Edit again... 

And so on. Surprising that 37Signals got it so wrong, considering their focus on making their products customer friendly.</description>
		<content:encoded><![CDATA[<p>Hi Matthew, I stopped using Writeboards the moment we were able to use Google Docs. (and now use Google Sites for project documentation). </p>
<p>The problem with Writeboards is that the process is all wrong:</p>
<p>1. View (assuming it&#8217;s an existing document</p>
<p>2. Click Edit, to edit a paragraph</p>
<p>3. Wait for the editor to load</p>
<p>4. Scroll down &amp; Squint in order to find the paragraph that you wanted to edit. (let&#8217;s say you want to insert a small table, for which you&#8217;ll need to know HTML)</p>
<p>5. Click &#8216;Save as newest version&#8217; and wait again to see latest version. </p>
<p>6. Oops! You forgot a closing  somewhere! (or to bold a word, or a numbered list looks wrong)</p>
<p>7. Click Edit again&#8230; </p>
<p>And so on. Surprising that 37Signals got it so wrong, considering their focus on making their products customer friendly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/comment-page-1/#comment-1384</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 31 Jan 2010 23:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/#comment-1384</guid>
		<description>Hi Matthew, I stopped using Writeboards the moment we were able to use Google Docs. (and now use Google Sites for project documentation). 

The problem with Writeboards is that the process is all wrong:

1. View (assuming it&#039;s an existing document

2. Click Edit, to edit a paragraph

3. Wait for the editor to load

4. Scroll down &amp; Squint in order to find the paragraph that you wanted to edit. (let&#039;s say you want to insert a small table, for which you&#039;ll need to know HTML)

5. Click &#039;Save as newest version&#039; and wait again to see latest version. 

6. Oops! You forgot a closing  somewhere! (or to bold a word, or a numbered list looks wrong)

7. Click Edit again... 

And so on. Surprising that 37Signals got it so wrong, considering their focus on making their products customer friendly.</description>
		<content:encoded><![CDATA[<p>Hi Matthew, I stopped using Writeboards the moment we were able to use Google Docs. (and now use Google Sites for project documentation). </p>
<p>The problem with Writeboards is that the process is all wrong:</p>
<p>1. View (assuming it&#8217;s an existing document</p>
<p>2. Click Edit, to edit a paragraph</p>
<p>3. Wait for the editor to load</p>
<p>4. Scroll down &amp; Squint in order to find the paragraph that you wanted to edit. (let&#8217;s say you want to insert a small table, for which you&#8217;ll need to know HTML)</p>
<p>5. Click &#8216;Save as newest version&#8217; and wait again to see latest version. </p>
<p>6. Oops! You forgot a closing  somewhere! (or to bold a word, or a numbered list looks wrong)</p>
<p>7. Click Edit again&#8230; </p>
<p>And so on. Surprising that 37Signals got it so wrong, considering their focus on making their products customer friendly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Guay</title>
		<link>http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/comment-page-1/#comment-19</link>
		<dc:creator>Matthew Guay</dc:creator>
		<pubDate>Tue, 12 Jan 2010 05:51:31 +0000</pubDate>
		<guid isPermaLink="false">http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/#comment-19</guid>
		<description>So were you using Writeboard or PBwiki?  I don&#039;t really remember with PBwiki, but it seems both of them didn&#039;t highlight who did what.  Writeboard did list revisions so with the name of the person who had edited a section, though, and you could easily compare 2 revisions to see what they had added/edited.  So that was helpful.

Nice to see you here, and let me know if I can change/add/improve anything!  I&#039;ll try to have frequent content/updates, so check back!</description>
		<content:encoded><![CDATA[<p>So were you using Writeboard or PBwiki?  I don&#8217;t really remember with PBwiki, but it seems both of them didn&#8217;t highlight who did what.  Writeboard did list revisions so with the name of the person who had edited a section, though, and you could easily compare 2 revisions to see what they had added/edited.  So that was helpful.</p>
<p>Nice to see you here, and let me know if I can change/add/improve anything!  I&#8217;ll try to have frequent content/updates, so check back!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew</title>
		<link>http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/comment-page-1/#comment-1383</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Tue, 12 Jan 2010 05:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/#comment-1383</guid>
		<description>So were you using Writeboard or PBwiki?  I don&#039;t really remember with PBwiki, but it seems both of them didn&#039;t highlight who did what.  Writeboard did list revisions so with the name of the person who had edited a section, though, and you could easily compare 2 revisions to see what they had added/edited.  So that was helpful.

Nice to see you here, and let me know if I can change/add/improve anything!  I&#039;ll try to have frequent content/updates, so check back!</description>
		<content:encoded><![CDATA[<p>So were you using Writeboard or PBwiki?  I don&#8217;t really remember with PBwiki, but it seems both of them didn&#8217;t highlight who did what.  Writeboard did list revisions so with the name of the person who had edited a section, though, and you could easily compare 2 revisions to see what they had added/edited.  So that was helpful.</p>
<p>Nice to see you here, and let me know if I can change/add/improve anything!  I&#8217;ll try to have frequent content/updates, so check back!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Davis</title>
		<link>http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/comment-page-1/#comment-18</link>
		<dc:creator>Louis Davis</dc:creator>
		<pubDate>Tue, 12 Jan 2010 05:01:18 +0000</pubDate>
		<guid isPermaLink="false">http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/#comment-18</guid>
		<description>Matt,

I had to deal with the same wiki in my final class at UNT this past semester. One thing that was challenging was that revisions were difficult to note unless someone chose another color or font that distinguished them from others. One nice part was that it allowed you to see who was really working on the team project. It was not hard to figure out who was doing their part anyway.</description>
		<content:encoded><![CDATA[<p>Matt,</p>
<p>I had to deal with the same wiki in my final class at UNT this past semester. One thing that was challenging was that revisions were difficult to note unless someone chose another color or font that distinguished them from others. One nice part was that it allowed you to see who was really working on the team project. It was not hard to figure out who was doing their part anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Davis</title>
		<link>http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/comment-page-1/#comment-1382</link>
		<dc:creator>Louis Davis</dc:creator>
		<pubDate>Tue, 12 Jan 2010 05:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://techinch.com/2010/01/11/writeboard-class-projects-reinvented/#comment-1382</guid>
		<description>Matt,

I had to deal with the same wiki in my final class at UNT this past semester. One thing that was challenging was that revisions were difficult to note unless someone chose another color or font that distinguished them from others. One nice part was that it allowed you to see who was really working on the team project. It was not hard to figure out who was doing their part anyway.</description>
		<content:encoded><![CDATA[<p>Matt,</p>
<p>I had to deal with the same wiki in my final class at UNT this past semester. One thing that was challenging was that revisions were difficult to note unless someone chose another color or font that distinguished them from others. One nice part was that it allowed you to see who was really working on the team project. It was not hard to figure out who was doing their part anyway.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced

Served from: techinch.com @ 2012-05-18 09:27:57 -->
