<?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: Habemus Dialogum &#8211; We Have a Dialog</title>
	<atom:link href="http://culturedcode.com/2008/02/habemus-dialogum-we-have-a-dialog.html/feed" rel="self" type="application/rss+xml" />
	<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html</link>
	<description>We make Things.</description>
	<lastBuildDate>Mon, 04 Apr 2011 16:24:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: ununcarne</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-2#comment-318</link>
		<dc:creator>ununcarne</dc:creator>
		<pubDate>Sun, 24 Feb 2008 16:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-318</guid>
		<description>I am necessary wish to find</description>
		<content:encoded><![CDATA[<p>I am necessary wish to find</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The evolution of task management (Things review)</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-2#comment-317</link>
		<dc:creator>The evolution of task management (Things review)</dc:creator>
		<pubDate>Sat, 23 Feb 2008 23:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-317</guid>
		<description>[...] them, and give us detailed information about what is happening on their side. One great example is this blog post in which they describe the evolution of their &#8220;recurring task&#8221; dialog, their design [...]</description>
		<content:encoded><![CDATA[<p>[...] them, and give us detailed information about what is happening on their side. One great example is this blog post in which they describe the evolution of their &#8220;recurring task&#8221; dialog, their design [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jürgen</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-2#comment-306</link>
		<dc:creator>Jürgen</dc:creator>
		<pubDate>Tue, 19 Feb 2008 15:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-306</guid>
		<description>@Case Larsen: The &quot;xx days/weeks etc. after previous todo is completed&quot; option might be for you. Visualization of a timeline is indeed interesting. In particular for people who use dates a lot (I don&#039;t). It might be nice addition to Things, provided it is implemented in a beautiful, simple, and unobtrusive/optional way.

@David Schloss: Hourly based reminders will not come soon. Right now the workflow of Things is based on days. Allowing hours would open up a completely new chapter. It might be useful though. But before diving into it we are certainly going to have a careful look at use cases o find out how a meaningful implementation might look like. After all, we don&#039;t want to simply copy the existing functionality in iCal.

@Mario Braun: Sure, simply an oversight.</description>
		<content:encoded><![CDATA[<p>@Case Larsen: The &#8220;xx days/weeks etc. after previous todo is completed&#8221; option might be for you. Visualization of a timeline is indeed interesting. In particular for people who use dates a lot (I don&#8217;t). It might be nice addition to Things, provided it is implemented in a beautiful, simple, and unobtrusive/optional way.</p>
<p>@David Schloss: Hourly based reminders will not come soon. Right now the workflow of Things is based on days. Allowing hours would open up a completely new chapter. It might be useful though. But before diving into it we are certainly going to have a careful look at use cases o find out how a meaningful implementation might look like. After all, we don&#8217;t want to simply copy the existing functionality in iCal.</p>
<p>@Mario Braun: Sure, simply an oversight.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mario Braun</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-2#comment-305</link>
		<dc:creator>Mario Braun</dc:creator>
		<pubDate>Tue, 19 Feb 2008 13:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-305</guid>
		<description>Could you please try to make all your dialogues accesible by keyword as well?

In the current public version for example, I cannot access the mini calender for the due date by keyboard, only by mouse.</description>
		<content:encoded><![CDATA[<p>Could you please try to make all your dialogues accesible by keyword as well?</p>
<p>In the current public version for example, I cannot access the mini calender for the due date by keyboard, only by mouse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Schloss</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-1#comment-303</link>
		<dc:creator>David Schloss</dc:creator>
		<pubDate>Mon, 18 Feb 2008 20:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-303</guid>
		<description>What a great walkthrough of a process. 

Is there going to be a way to set a TIME of both a dated item and a recurring process? Because many recurring processes have to happen for us at a specific time. For example our payroll has to be called in between 4pm and 5pm every two weeks. Having a reminder for the date doesn&#039;t help trigger the person to do the payroll at exactly the right time, so they have to go to ical to do a time based reminder.</description>
		<content:encoded><![CDATA[<p>What a great walkthrough of a process. </p>
<p>Is there going to be a way to set a TIME of both a dated item and a recurring process? Because many recurring processes have to happen for us at a specific time. For example our payroll has to be called in between 4pm and 5pm every two weeks. Having a reminder for the date doesn&#8217;t help trigger the person to do the payroll at exactly the right time, so they have to go to ical to do a time based reminder.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Case Larsen</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-1#comment-301</link>
		<dc:creator>Case Larsen</dc:creator>
		<pubDate>Mon, 18 Feb 2008 05:52:17 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-301</guid>
		<description>i respect your dialog choices -- preciseness, but an option to not impose a due date.

Does that mean that the task is recreated periodically, but no specific due date is assigned, so it shows up in the &quot;next&quot; focus.  I assume multiple copies don&#039;t get created if you just really don&#039;t complete it soon enough.

My preference (with paper planning) was to use something that visualized a timeline rather than a calendar based mechanism since i didn&#039;t need exactness of date but rather a feeling of adequate attention over time.

http://tinyurl.com/2d5rko

i would love for this analog method to inspire a digital implementation since right now, i&#039;ve replaced all my paper based task tracking using Things except for this particular aspect.</description>
		<content:encoded><![CDATA[<p>i respect your dialog choices &#8212; preciseness, but an option to not impose a due date.</p>
<p>Does that mean that the task is recreated periodically, but no specific due date is assigned, so it shows up in the &#8220;next&#8221; focus.  I assume multiple copies don&#8217;t get created if you just really don&#8217;t complete it soon enough.</p>
<p>My preference (with paper planning) was to use something that visualized a timeline rather than a calendar based mechanism since i didn&#8217;t need exactness of date but rather a feeling of adequate attention over time.</p>
<p><a href="http://tinyurl.com/2d5rko" rel="nofollow">http://tinyurl.com/2d5rko</a></p>
<p>i would love for this analog method to inspire a digital implementation since right now, i&#8217;ve replaced all my paper based task tracking using Things except for this particular aspect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RichardM</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-1#comment-299</link>
		<dc:creator>RichardM</dc:creator>
		<pubDate>Fri, 15 Feb 2008 04:53:26 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-299</guid>
		<description>@Jorge - In Prefs - General, click on box next to the &quot;Enable hotkey for Quick Entry Panel&quot; and press F6. Now F6 works the same as iGTD

Great App guys - can&#039;t wait for 1.0.</description>
		<content:encoded><![CDATA[<p>@Jorge &#8211; In Prefs &#8211; General, click on box next to the &#8220;Enable hotkey for Quick Entry Panel&#8221; and press F6. Now F6 works the same as iGTD</p>
<p>Great App guys &#8211; can&#8217;t wait for 1.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-1#comment-297</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 14 Feb 2008 21:47:53 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-297</guid>
		<description>Duh. Nevermind. I see the &quot;Today&quot; option is already covered. Sorry. More caffeine!</description>
		<content:encoded><![CDATA[<p>Duh. Nevermind. I see the &#8220;Today&#8221; option is already covered. Sorry. More caffeine!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-1#comment-296</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 14 Feb 2008 21:45:03 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-296</guid>
		<description>We would like to see the option to automatically set recurring events for &quot;Today&quot; as they are created. Is that a planned feature/option?</description>
		<content:encoded><![CDATA[<p>We would like to see the option to automatically set recurring events for &#8220;Today&#8221; as they are created. Is that a planned feature/option?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Beck</title>
		<link>http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html/comment-page-1#comment-295</link>
		<dc:creator>Daniel Beck</dc:creator>
		<pubDate>Thu, 14 Feb 2008 16:49:20 +0000</pubDate>
		<guid isPermaLink="false">http://culturedcode.com/things/blog/2008/02/habemus-dialogum-we-have-a-dialog.html#comment-295</guid>
		<description>Iannis Zannos:
Why don&#039;t you use iCal for events? If iCal doesn&#039;t meet your calendaring needs, why should an app with a different focus? More like crossing the border to featuritis, since the power of Things is its simplicity. But that&#039;s just my opinion.
I thought very briefly about moving to Things with events (lectures, meetings etc) myself, but decided that a task management app shouldn&#039;t be abused as calendar. I use iCal with the incredibly useful iCalViewer, and it works great.
Regards,
Daniel</description>
		<content:encoded><![CDATA[<p>Iannis Zannos:<br />
Why don&#8217;t you use iCal for events? If iCal doesn&#8217;t meet your calendaring needs, why should an app with a different focus? More like crossing the border to featuritis, since the power of Things is its simplicity. But that&#8217;s just my opinion.<br />
I thought very briefly about moving to Things with events (lectures, meetings etc) myself, but decided that a task management app shouldn&#8217;t be abused as calendar. I use iCal with the incredibly useful iCalViewer, and it works great.<br />
Regards,<br />
Daniel</p>
]]></content:encoded>
	</item>
</channel>
</rss>

