The project title was added to the wrong panel which caused side effect of showing a title when
creating a new template. Moved the previous code it is only shown when editing a template.
Also changed it to read the title from the database using the LoadableDetachableModel pattern.
Now the project title should only be shown when editing an existing template.
Previously max available points where only updated when you added a new criterion.
It is beneficial that the user can see the max available points as they have completed editing the
template without having to click on the create button or add a new criterion.
Previously a user could click on the create button before they had chosen a
grading template project type from the Project type dropdown.
This would result in a runtime exception, and possibly in an unhappy user.
To protect the user from "jumping the gun", the Create button will only become visible
after the user has selected a Project type from the dropdown menu.
When you added new criteria you only got to set the criterion title, type, flag and point but you had to manually add the requirements for the first criterion.
Now when you add a new criterion the new criterion will by default add the requirement for the points.
reverted a previous change in the for loop the correct condition was to check against 0, I accidently turned that to 1 in a previous commit. Also added a comment to try and explain what that condition checks for.
Previously if you created a new grading template chose a date for `Valid from` field and then added a criterion.
The valid from date would reset to null. This would create a validation error on save.
This creates unnecessary confusion for the user.
Now when you have chosen a date and then choose to add a criterion to the template the date does not reset.
The reason for this was that the AutoSave() added to the field was using the wrong event to trigger the setValidFrom().
Since we use bootstraps date picker we have to trigger on "changeDate" event.
When adding a new criteria to a template the default value of `Points required to pass` was `0` (zero).
Now when you add a new criterion to a template the `Points required to pass` default to `1` (one).
When you chose to edit a template you could not see what type the template is.
For example if it was a bachelor or master type template.
Now when you choose to edit a grading template the type will be shown as a heading,
so you can more easily see what type of template you are currently editing.
The heading will read:
`You are editing a <type> grading template.`
The <type> will display the correct type of the grading template you are editing.
Open to change of what exactly the heading will display if anyone has a better idea for it.
Grading template did not have any way to alert the user that changes had been made when editing a template.
Added a way to detect and alert the user when changes have been made on the grading template they are editing. If the user removes his changes, so the template is in the same state as it was when the user started editing the template the alert will disappear.
The project title was added to the wrong panel which caused side effect of showing a title when
creating a new template. Moved the previous code it is only shown when editing a template.
Also changed it to read the title from the database using the LoadableDetachableModel pattern.
Now the project title should only be shown when editing an existing template.
Previously max available points where only updated when you added a new criterion.
It is beneficial that the user can see the max available points as they have completed editing the
template without having to click on the create button or add a new criterion.
Previously a user could click on the create button before they had chosen a
grading template project type from the Project type dropdown.
This would result in a runtime exception, and possibly in an unhappy user.
To protect the user from "jumping the gun", the Create button will only become visible
after the user has selected a Project type from the dropdown menu.
When you added new criteria you only got to set the criterion title, type, flag and point but you had to manually add the requirements for the first criterion.
Now when you add a new criterion the new criterion will by default add the requirement for the points.
reverted a previous change in the for loop the correct condition was to check against 0, I accidently turned that to 1 in a previous commit. Also added a comment to try and explain what that condition checks for.
Previously if you created a new grading template chose a date for `Valid from` field and then added a criterion.
The valid from date would reset to null. This would create a validation error on save.
This creates unnecessary confusion for the user.
Now when you have chosen a date and then choose to add a criterion to the template the date does not reset.
The reason for this was that the AutoSave() added to the field was using the wrong event to trigger the setValidFrom().
Since we use bootstraps date picker we have to trigger on "changeDate" event.
When adding a new criteria to a template the default value of `Points required to pass` was `0` (zero).
Now when you add a new criterion to a template the `Points required to pass` default to `1` (one).
When you chose to edit a template you could not see what type the template is.
For example if it was a bachelor or master type template.
Now when you choose to edit a grading template the type will be shown as a heading,
so you can more easily see what type of template you are currently editing.
The heading will read:
`You are editing a <type> grading template.`
The <type> will display the correct type of the grading template you are editing.
Open to change of what exactly the heading will display if anyone has a better idea for it.
Grading template did not have any way to alert the user that changes had been made when editing a template.
Added a way to detect and alert the user when changes have been made on the grading template they are editing. If the user removes his changes, so the template is in the same state as it was when the user started editing the template the alert will disappear.
