From: vincenegri (vince.negri_at_gmail.com)
Date: Mon Nov 07 2005 - 15:56:39 CET
From: vincenegri <vince.negri@gmail.com> Message-ID: <17fe.436f6b27@www.taskjuggler.org> Date: Mon, 7 Nov 2005 15:56:39 +0100 (CET) Subject: [taskjuggler-devel] Re: Display of Tasks with subtasks
Quote:
> Once all the sub tasks have been scheduled, TJ determines the time frame of the container tasks. But it must respect any date that the user has given. I cannot shorten a container just because no sub tasks extends to this date.
Yes, I can see the reasoning - if the user has specified a date, honour that date where possible. In my case the issue arises partly because I was exploiting the fact that for a non-container task, TJ does not issue a warning if the task has to start later than the start date.
I was exploiting that fact because I wanted to avoid making all the top-level tasks depend on something (each top-level task must have either a start date or depend on something, as you know) since that created lots of lines in the Gantt - unnecessary lines, IMHO, since "obviously" all the top level tasks depend on the start of the project.
I suppose what I really wanted all along is to be able to say for a top-level task (whether it is a container task or not) "schedule this asap after the project start date, but there are no explicit dependencies." Specifying a start that is equal to the project start date has the right scheduling effect, but with the side-effect that TJ thinks that the start date is significant.
Quote:
> I've reworked the arrow routing algorithm yesterday. It's already in the SVN snapshot. You might want to give it a try.
Thanks, I will try it out.
-- To unsubscribe, email: taskjuggler-devel-unsubscribe@suse.com For additional commands, email: taskjuggler-devel-help@suse.com
This archive was generated by hypermail 2.1.7 : Mon Nov 07 2005 - 15:56:42 CET