From: Chris Schlaeger (cs_at_suse.de)
Date: Mon Jun 23 2003 - 16:18:48 CEST
From: Chris Schlaeger <cs@suse.de> Date: Mon, 23 Jun 2003 16:18:48 +0200 Message-Id: <200306231618.52698.cs@suse.de> Subject: Re: [taskjuggler] minstart
On Thursday 19 June 2003 10:24, g3tq-jcrq@dea.spamcon.org wrote:
> Hello !
>
> Once the project plan is established, adding unexpected tasks and in
> general doing some shuffling is quite hazardous. Things that were in the
> past (and were done) may be shifted in the future, and vice-versa just by
> adding a couple items or changing a resource in some (future) task.
>
> What is the best recommended way of handling this ?
Do you know why the shuffling happens? Modifications of future tasks or
additions should not affect past tasks. That is, unless you heavyly mix ALAP
and ASAP scheduling modes for your tasks. TJ schedules tasks from early to
late. Tasks that cannot be scheduled, will be ignored until enough data is
known to schedule them.
I agree with you, that this shuffling is really annoying. But before we try to
come up with a tool to fix this, I'd like to make sure, that the shuffling
can't be avoided by changing the way the project is specified.
> Thanks for all, floks ! this is the best open source project planner that I
> have found. Keep focusing on the algorithmics, not on the GUI !
I probably wont work on a GUI. But others are working on viewers already.
Chris
-- KDE 3.1: Conquer your Enterprise Desktop! See http://www.kde.org! GPG Key: 1024D/0500838B A5FE C051 2AFC 9A14 768A 5125 5829 5750 0500 838B
This archive was generated by hypermail 2.1.7 : Mon Jun 23 2003 - 16:20:28 CEST