Re: [taskjuggler] A Question or a feature request

From: Chris Schlaeger (cs_at_suse.de)
Date: Mon Feb 03 2003 - 15:45:19 CET

  • Next message: Bombadil: "Re: [taskjuggler] A Question or a feature request"
    From: Chris Schlaeger <cs@suse.de>
    Date: Mon, 3 Feb 2003 15:45:19 +0100
    Message-Id: <200302031545.19061.cs@suse.de>
    Subject: Re: [taskjuggler] A Question or a feature request
    

    Hi,

    On Saturday 01 February 2003 00:22, Bombadil wrote:
    > Hi,
    > I am starting to use taskjuggler and I really like it.

    glad to hear this.

    > Actually I have to schelude a new project , and I am using its data to
    > practise with taskjuggler.
    >
    > One of the problems I use to have is , for example , suppose I have two
    > tasks (A&B) , and the second (B) depends from the first (A) , but supose
    > the second task can start when the first task reach 50% of realization.
    >
    > The only way I have to represent it (I think) is to divide the fisrt task
    > in two tasks (A1&A2) , and make second task (B) depends from the first part
    > (A1) of the first task (A).
    >
    > ... I don't know it's clear , well the problem is that this happens
    > habitually and I use to work with a lot of tasks , so I have to divide
    > too much tasks and the project loose visibility and clarity.
    >
    > The question is , Does exist an easy way to define such "relative" or
    > "soft" dependencies with taskjuggler? , and if not , Don't you think it
    > could be an interesting feature for taskjuggler?

    There is no concept of soft dependencies in TJ and there are no plans to add
    it. If I understand you correctly you have really a situation like this:

    task a1 "A1" {
    }

    task a2 "A2" {
    }

    task b "B" {
      depends !a1
    }

    But you don't want to crowd your reports with A1/A2 instead of A. A possible
    solution would be

    task a "A" {
      flag hideDetails
      task a1 "A1" {
      }
      task a2 "A2" {
      }
    }

    task b "B" {
      depends !a.a1
    }

    htmltaskreport "foo.html" {
      rolluptask hideDetails
    }

    This way you would have all the information in your project plan but your
    reports still don't look too crowded. Of course it's a little bit of writing
    work, but you might be able to use some macros.

    Chris

    -- 
    KDE 3.1: Conquer your Enterprise Desktop!
    http://www.kde.org
    -- 
    To unsubscribe, email the address listed in the List-Unsubscribe header
    For additional commands, email: taskjuggler-help@suse.com
    

  • Next message: Bombadil: "Re: [taskjuggler] A Question or a feature request"

    This archive was generated by hypermail 2.1.6 : Mon Feb 03 2003 - 15:45:40 CET