This change implements the behaviour described in the analysis that you can
easily understand with the following example:
1) Initial scenario:
* Task leaf "A" (0 hours)
* Task leaf "B" (20 hours)
2) Indent task leaf "B"
3) Final scenario:
* Task container "A" (20 hours)
|- Task leaf "B" (20 hours)
FEA: ItEr76S13WBSSettingUpBehavior
Now a new container is created, but the older leaf is not added again if it is
empty (wich means that it has zero hours, no criteria, no progresses, ...)
FEA: ItEr76S13WBSSettingUpBehavior
The order in the deletion of the different objects related with the task was
wrong and it was causing an exception.
Moreover, the exception was breaking the flow of execution in our application
and preventing that the size of container was updated.
FEA: ItEr76S04BugFixing
We are finally considering that information on the projects having assignment or
not, is not relevant enough, so we are not specifiying a different style for
.standard-task.assigned.project-closed elements
FEA: ItEr76S04BugFixing
If a template is selected the option of manually setting a code is disabled, so
it's clearer if this option is fillable or not after the template one.
FEA: ItEr76S04BugFixing
* If a template is selected, the 'generate code' checkbox is automatically set and disabled
* When selecting a project, start project date is calculated with the current day plus template start delay
* Deadline is calculated as start project date plus template duration till deadline
FEA: ItEr76S04BugFixing
Add French translation for main translation files (.pot) and report files
(.properties).
Translation mainly done by Philippe Poumaroux with contributions by Stephane
Ayache and Guillaume Postaire.
The method belongsClosedProject() was not correctly implemented for
TaskMilestone objects, I've added the correct implementation for them.
FEA: ItEr76S04BugFixing
Redraw was being done every time a task was rendered and one last time when all
the tasks are rendered. Doing only the last redraw is enough.
This change should improve performance when opening containers.
FEA: ItEr76S04BugFixing
To do that we had to add an attribute in DependencyComponent to store the
listener and a method in Task to be able to delete visibility listeners.
This listener was causing that deleted tasks re-appeared when containers were
closed and opened again.
FEA: ItEr76S04BugFixing
Since the start date depends on the value of the end date and vice versa, a
recursive, infinite loop can happen when both dates are going to be validated.
FEA: ItEr76S04BugFixing
They are calculated by default as the start and end dates of the first and last
open projects, but the user had no feedback on which were those dates.
FEA: ItEr76S04BugFixing
