<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Voo2do vs. Backpack</title>
	<link>http://blog.voo2do.com/2005/09/05/voo2do-vs-backpack/</link>
	<description>news and tips for users of voo2do.com : web-based task tracking</description>
	<pubDate>Fri, 05 Sep 2008 22:01:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Voo2do vs. Backpack by: Bien batido y revuelto &#187; oo2do : un gestor de tareas</title>
		<link>http://blog.voo2do.com/2005/09/05/voo2do-vs-backpack/#comment-27</link>
		<pubDate>Thu, 22 Sep 2005 11:49:13 +0000</pubDate>
		<guid>http://blog.voo2do.com/2005/09/05/voo2do-vs-backpack/#comment-27</guid>
					<description>[...] No me preguntéis cómo pero de casualidad me he topado con voo2do, una aplicación web para gestionar tareas y listas to-do. Está en desarrollo (podemos seguirlo en su blog) y para hacernos una idea, es comparable a Backpack (o quizás incluso ta-da lists). De heco, publican una comparación de voo2do frente a Backpack. [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] No me preguntéis cómo pero de casualidad me he topado con voo2do, una aplicación web para gestionar tareas y listas to-do. Está en desarrollo (podemos seguirlo en su blog) y para hacernos una idea, es comparable a Backpack (o quizás incluso ta-da lists). De heco, publican una comparación de voo2do frente a Backpack. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Voo2do vs. Backpack by: miahz.com &#187; Blog Archive &#187; Design Trend</title>
		<link>http://blog.voo2do.com/2005/09/05/voo2do-vs-backpack/#comment-23</link>
		<pubDate>Tue, 20 Sep 2005 06:24:51 +0000</pubDate>
		<guid>http://blog.voo2do.com/2005/09/05/voo2do-vs-backpack/#comment-23</guid>
					<description>[...] Are seals a new web design trend? I mean like the little gold foil stickers on diplomas and other important documents? Noticed it on the header at inforedesign [via], and recalled seeing one on the recently revamped ALA: &amp;#8220;The numerical bug that sits atop the logo and astride the nav bar makes each issue feel like an important limited edition.&amp;#8221; Seems like i&amp;#8217;ve seen &amp;#8216;em elsewhere too. [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] Are seals a new web design trend? I mean like the little gold foil stickers on diplomas and other important documents? Noticed it on the header at inforedesign [via], and recalled seeing one on the recently revamped ALA: &#8220;The numerical bug that sits atop the logo and astride the nav bar makes each issue feel like an important limited edition.&#8221; Seems like i&#8217;ve seen &#8216;em elsewhere too. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Voo2do vs. Backpack by: Shimon</title>
		<link>http://blog.voo2do.com/2005/09/05/voo2do-vs-backpack/#comment-21</link>
		<pubDate>Sun, 18 Sep 2005 15:05:05 +0000</pubDate>
		<guid>http://blog.voo2do.com/2005/09/05/voo2do-vs-backpack/#comment-21</guid>
					<description>Meng,

Currently, you can only associate projects with views.  A couple of people have pointed out that this doesn't work well for GTD, and I'd like to address that.  I'm thinking of adding a right-click menu on each task in the future, and perhaps I could have a &quot;Route to view&quot; option there.  So by default a task would be viewed in its project's default view, but you could alter views on a per-task basis.

Would that work for you?</description>
		<content:encoded><![CDATA[	<p>Meng,</p>
	<p>Currently, you can only associate projects with views.  A couple of people have pointed out that this doesn&#8217;t work well for GTD, and I&#8217;d like to address that.  I&#8217;m thinking of adding a right-click menu on each task in the future, and perhaps I could have a &#8220;Route to view&#8221; option there.  So by default a task would be viewed in its project&#8217;s default view, but you could alter views on a per-task basis.</p>
	<p>Would that work for you?
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Voo2do vs. Backpack by: Meng Kuan</title>
		<link>http://blog.voo2do.com/2005/09/05/voo2do-vs-backpack/#comment-20</link>
		<pubDate>Sun, 18 Sep 2005 06:48:24 +0000</pubDate>
		<guid>http://blog.voo2do.com/2005/09/05/voo2do-vs-backpack/#comment-20</guid>
					<description>Just took Voo2do for a spin. Was looking for something that I can implement GTD (Getting Things Done) system with and this seems like a nice fit. However, one thing I find that does not fit as nicely is the use of Views and its use as contexts (GTD terminology). Currently a project can only be associated with one view. However, if you have several tasks in a project and you need them to be in separate views then this can't be done. For example, I have 2 tasks in a project. The first task can only be done at home (view 1) while the other is when I am running errands outside (view 2). Can the association with views (contexts) done at task level and not at project level?</description>
		<content:encoded><![CDATA[	<p>Just took Voo2do for a spin. Was looking for something that I can implement GTD (Getting Things Done) system with and this seems like a nice fit. However, one thing I find that does not fit as nicely is the use of Views and its use as contexts (GTD terminology). Currently a project can only be associated with one view. However, if you have several tasks in a project and you need them to be in separate views then this can&#8217;t be done. For example, I have 2 tasks in a project. The first task can only be done at home (view 1) while the other is when I am running errands outside (view 2). Can the association with views (contexts) done at task level and not at project level?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
