From: Chris Schlaeger (cs_at_suse.de)
Date: Tue Feb 04 2003 - 22:20:22 CET
From: Chris Schlaeger <cs@suse.de> Date: Tue, 4 Feb 2003 22:20:22 +0100 Message-Id: <200302042220.24181.cs@suse.de> Subject: Re: [taskjuggler] A Question or a feature request
On Tuesday 04 February 2003 21:00, Bombadil wrote:
> Ok , it's a solution that avoid the loose of visibility ,
> anyway I'll have to write qiute a lot ... welll until now
> it's the best solution.
You can try to use a macro like this:
macro SubTasks [
flag hideDetails
task a1 "A1" {
length ${1}
}
task a2 "A2" {
length ${2}
}
]
task a "A" {
${SubTasks "5d" "5d"}
}
task b "B" {
depends !a.a1
}
This reduces the overhead to the macro declaration plus 1 line for each task.
Certainly the macro does not really increase the readability of your project
file.
Chris
> > > 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
-- 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
This archive was generated by hypermail 2.1.6 : Tue Feb 04 2003 - 22:20:29 CET