<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Inbox Blinders?</title>
	<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/</link>
	<description></description>
	<pubDate>Thu, 20 Nov 2008 09:05:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.3</generator>

	<item>
		<title>by: Graham</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-78</link>
		<pubDate>Fri, 01 Sep 2006 00:02:20 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-78</guid>
					<description>You may want to take a look at Lotus Agenda and see if you can take anything from it.  It was an extremely flexible database for managing 'things'.  There were no boundaries and little structure natively but both could be imposed by the user.  It was released as DOS freeware.

http://en.wikipedia.org/wiki/Lotus_Agenda

The program itself was way ahead of its time and still has a dedicated fan base.  Its successor, 'chandler' has lofty goals but seems to do too many things without doing any of them well.</description>
		<content:encoded><![CDATA[<p>You may want to take a look at Lotus Agenda and see if you can take anything from it.  It was an extremely flexible database for managing &#8216;things&#8217;.  There were no boundaries and little structure natively but both could be imposed by the user.  It was released as DOS freeware.</p>
<p><a href='http://en.wikipedia.org/wiki/Lotus_Agenda' rel='nofollow'>http://en.wikipedia.org/wiki/Lotus_Agenda</a></p>
<p>The program itself was way ahead of its time and still has a dedicated fan base.  Its successor, &#8216;chandler&#8217; has lofty goals but seems to do too many things without doing any of them well.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jon</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-58</link>
		<pubDate>Fri, 18 Aug 2006 14:09:55 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-58</guid>
					<description>Bob: Thanks for the input! You're on the list.

From your comment, it sounds like you are picturing the Inbox as being in your mail application, so one clarification is probably in order (since there isn't much in the way of screenshots on the site yet) -- the app itself has an Inbox that can catch items as they come up. This is like the physical Inbox in Allen's system, and this is the part of the app that will allow both the blinders or a full stack view, depending on the user's selection from a filter bar above the list.

My desire is to also connect this with Mail so that items that get tagged show up in my app. I'll check into the Thunderbird plugin option as it is a nice client and open source too. Tagging an entire thread is interesting too and I could see that being very useful. Once I get into the weeds a little more on this one, it may deserve its own blog post.</description>
		<content:encoded><![CDATA[<p>Bob: Thanks for the input! You&#8217;re on the list.</p>
<p>From your comment, it sounds like you are picturing the Inbox as being in your mail application, so one clarification is probably in order (since there isn&#8217;t much in the way of screenshots on the site yet) &#8212; the app itself has an Inbox that can catch items as they come up. This is like the physical Inbox in Allen&#8217;s system, and this is the part of the app that will allow both the blinders or a full stack view, depending on the user&#8217;s selection from a filter bar above the list.</p>
<p>My desire is to also connect this with Mail so that items that get tagged show up in my app. I&#8217;ll check into the Thunderbird plugin option as it is a nice client and open source too. Tagging an entire thread is interesting too and I could see that being very useful. Once I get into the weeds a little more on this one, it may deserve its own blog post.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bob Sloan</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-57</link>
		<pubDate>Fri, 18 Aug 2006 13:31:20 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-57</guid>
					<description>I'd vote for the blinders--this part of GTD discipline really helps me.  BUT, for me, I'd want an option to get next message, OR, next message and its entire thread, since I often get threads to process. (In an ideal world, also a choice of Mail.app or Thunderbird, but that's probably much more work.)

I too would be very interested in being on the beta list.</description>
		<content:encoded><![CDATA[<p>I&#8217;d vote for the blinders&#8211;this part of GTD discipline really helps me.  BUT, for me, I&#8217;d want an option to get next message, OR, next message and its entire thread, since I often get threads to process. (In an ideal world, also a choice of Mail.app or Thunderbird, but that&#8217;s probably much more work.)</p>
<p>I too would be very interested in being on the beta list.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jon</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-53</link>
		<pubDate>Wed, 16 Aug 2006 12:56:14 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-53</guid>
					<description>umop: You're on the list.</description>
		<content:encoded><![CDATA[<p>umop: You&#8217;re on the list.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: umop</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-52</link>
		<pubDate>Wed, 16 Aug 2006 08:48:33 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-52</guid>
					<description>I just found this site.  I'm very interested in being on the beta list for this.  I'm currently using kGTD with some success.  Definitely looking for a replacement as updates seem to have ceased on it.</description>
		<content:encoded><![CDATA[<p>I just found this site.  I&#8217;m very interested in being on the beta list for this.  I&#8217;m currently using kGTD with some success.  Definitely looking for a replacement as updates seem to have ceased on it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: laurel</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-49</link>
		<pubDate>Tue, 15 Aug 2006 11:35:00 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-49</guid>
					<description>That sounds really great!</description>
		<content:encoded><![CDATA[<p>That sounds really great!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jon</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-48</link>
		<pubDate>Tue, 15 Aug 2006 02:14:32 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-48</guid>
					<description>Laurel, post anytime. I appreciate the input and value your opinion. The dependencies you mention are important to me as well and this is how I am building the lists -- when viewing tasks under a project, the tasks can be ordered in whatever manner you wish. The top one is the Next Action. When you check it off, the next one instantly becomes the Next Action. In the context view (@email for example), all of the actions or Next Actions can be ordered too. So, you can actually place a Next Action from ProjectA in front of one for ProjectB and the app will remember your preference.</description>
		<content:encoded><![CDATA[<p>Laurel, post anytime. I appreciate the input and value your opinion. The dependencies you mention are important to me as well and this is how I am building the lists &#8212; when viewing tasks under a project, the tasks can be ordered in whatever manner you wish. The top one is the Next Action. When you check it off, the next one instantly becomes the Next Action. In the context view (@email for example), all of the actions or Next Actions can be ordered too. So, you can actually place a Next Action from ProjectA in front of one for ProjectB and the app will remember your preference.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: laurel</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-47</link>
		<pubDate>Mon, 14 Aug 2006 15:46:12 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-47</guid>
					<description>Sorry, me again.  I can't remember if this has come up, but something else that is really key for me is dependencies.  Often there is a series of tasks on a project that have to be done in order.  It would be great to have the next one come up automatically when you've done one. (Hope that makes sense!)</description>
		<content:encoded><![CDATA[<p>Sorry, me again.  I can&#8217;t remember if this has come up, but something else that is really key for me is dependencies.  Often there is a series of tasks on a project that have to be done in order.  It would be great to have the next one come up automatically when you&#8217;ve done one. (Hope that makes sense!)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jon</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-45</link>
		<pubDate>Mon, 14 Aug 2006 05:23:09 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-45</guid>
					<description>Ok, laurel. You're on the list.</description>
		<content:encoded><![CDATA[<p>Ok, laurel. You&#8217;re on the list.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: laurel</title>
		<link>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-44</link>
		<pubDate>Sun, 13 Aug 2006 15:39:30 +0000</pubDate>
		<guid>http://www.kaboomerang.com/blog/2006/08/05/inbox-blinders/#comment-44</guid>
					<description>Just to say:  I'd be happy to beta as well.</description>
		<content:encoded><![CDATA[<p>Just to say:  I&#8217;d be happy to beta as well.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
