milistart.blogg.se - Ganttproject 2.7 tutorial

#Ganttproject 2.7 tutorial pdf#
#Ganttproject 2.7 tutorial archive#
#Ganttproject 2.7 tutorial code#

this discussion or many other similar by keywords "change dates"). Many people like GanttProject because it doesn't try to be too clever and get confused when tasks move even in those scenarios when they really have to move because of dependencies or because it is a summary task (see e.g. Not sure that MS Project behavior worth copying in this case. This is just my opinion - for reference I work in project management and am a MS Project user :) This occurs very frequently in practice, when working with complex sequence of activities, as it is difficult to find all the tasks which are dependent on a given task to be removed. As a result, if task 1 is subsequently increased in duration and its start date moves to after the start of task 3, a logical inconsistency occurs.

Automaticaly rescheduling task 3 to the project start date allows the user to immediately realise that it has become "unbound" and correct it by creating the dependency.Ĭonversely, leaving task 3 to its current date hides this problem. This is consistent with MS Projectįurther, the behaviour I suggest helps the user identify a common source of mistake: given a sequence of interdependent tasks 1 -> 2 -> 3, if task 2 is removed the user should manually add a dependency from 1 -> 3. If also no constraint exists, then the task should be rescheduled to the project start date (even if it is in the past). In fact, GanttProject schedules any newly created task to start on the project start date, which I think is the correct behaviour.įor consistency, I think the same should occur to a task when removing all its dependencies. When the "additional constraint" field is empty, a task should start asap (dependencies permitting).

start as late as possible without delaying tasks on the critical path.

start asap (this is the default we use in project management and is limited backwards to the project start date).

To elaborate, scheduling options for a task are: You can download GanttProject 2.In my opinion, it should be rescheduled to the project start date, as it is the earliest possible date.

#Ganttproject 2.7 tutorial code#

Unfortunately Project Hosting on Google Code which we are using stopped its download service. Please let us know if you notice any compatibility problems. We expect that files created in the previous versions of GanttProject should work fine in GP 2.7, and that GanttProject 2.6 can read files created in GP 2.7, skipping data related to newly added features of course. Please refer to installation instructions on our Wiki pages. You can run it on any Java-enabled platform (Windows, Mac OSX, Linux, etc.), provided that you can run java command from your terminal window.

#Ganttproject 2.7 tutorial archive#

GanttProject 2.7 requires Java 7 or Java 8 and is available as ZIP archive only.

#Ganttproject 2.7 tutorial pdf#

There is one removal: FOP based PDF export, which was deprecated since GP 2.5, is not included into GanttProject 2.7. There are a few less important changes, library updates, and so on.

This feature sits in the refactored Public Holidays dialog which is now way more functional. In GP 2.7 it is possible to add "exceptions" and make particular weekends working.

Such use case could not be represented in GanttProject previously. in Russia, if a holiday happens on Tuesday, it will be "merged" with the closest weekend, and Monday will be non-working too (thus we get 4 days looong weekend), but one of the next weekends will have one working day. One more highly requested calendar-related feature is ability to make working some particular weekend day.