From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yann Hodique Subject: Re: [PATCH 07/10] org-taskjuggler: make project umbrella task optional Date: Sun, 12 Aug 2012 10:03:28 +0200 Message-ID: References: <1344164044-15059-1-git-send-email-yann.hodique@gmail.com> <1344164044-15059-8-git-send-email-yann.hodique@gmail.com> <87393v9uvf.fsf@sbs.ch> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:32816) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T0TR8-0006GM-K0 for emacs-orgmode@gnu.org; Sun, 12 Aug 2012 04:22:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T0TR7-0005FD-DO for emacs-orgmode@gnu.org; Sun, 12 Aug 2012 04:22:14 -0400 Received: from plane.gmane.org ([80.91.229.3]:39421) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T0TR7-0005F4-66 for emacs-orgmode@gnu.org; Sun, 12 Aug 2012 04:22:13 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1T0TR6-0000tB-E6 for emacs-orgmode@gnu.org; Sun, 12 Aug 2012 10:22:12 +0200 Received: from home.hodique.info ([78.213.112.104]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 12 Aug 2012 10:22:12 +0200 Received: from yann.hodique by home.hodique.info with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 12 Aug 2012 10:22:12 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org >>>>> "Christian" == Christian Egli writes: > Yann Hodique writes: >> +(defcustom org-export-taskjuggler-keep-project-as-task t >> + "Whether to keep the project headline as an umbrella task for >> + all declared tasks. Setting this to nil will allow maintaining >> + completely separated task buckets, while still sharing the same >> + resources pool." > I'm trying to understand the use case here. If I understand correctly > the container headline will no longer unconditionally generate a root > task. So you could have multiple root tasks? Does this work in both > versions of tj? Yes, basically the use case is the following. >From an org code like: --8<---------------cut here---------------start------------->8--- * Main :taskjuggler_project: ** Task1 ** Task2 --8<---------------cut here---------------end--------------->8--- the default behavior is to generate something like --8<---------------cut here---------------start------------->8--- project main Main (} task main "Main" { task task1 "Task1" {} task task2 "Task2" {} } --8<---------------cut here---------------end--------------->8--- leading to a report like --8<---------------cut here---------------start------------->8--- 1. Main 1.1 Task1 1.2 Taks2 --8<---------------cut here---------------end--------------->8--- while the new (non-default) one would generate --8<---------------cut here---------------start------------->8--- project main Main {} task task1 "Task1" {} task task2 "Task2" {} --8<---------------cut here---------------end--------------->8--- leading to a report like --8<---------------cut here---------------start------------->8--- 1 Task1 2 Task2 --8<---------------cut here---------------end--------------->8--- I must confess this is mostly a way to avoid questions from people looking at the report, asking why my task numbers are all 1.x :) AFAICT it seems to work fine with either tj2 or tj3. I'm using tj3 only myself, but the UI of tj2 doesn't complain at all about those multiple root tasks. Thanks, Yann -- When faced with necessary actions, there are always choices. So long as the job gets done. -- COUNT HASIMIR FENRING, Dispatches from Arrakis