| 39 | \\ Templating system |
| 40 | \\ Day view |
| 41 | |
| 42 | = To Do = |
| 43 | * Change the label from 'Event' to 'Type' when selecting between |
| 44 | Project/Org/etc ('Event Name' -> 'Name') |
| 45 | * Change the resource name from 'table' to 'roster' (at least for the |
| 46 | user-visible CRUD strings) |
| 47 | * Rename 'Slots' as 'Shifts' (which also keeps consistency with the |
| 48 | use of Shifts elsewhere) |
| 49 | * I don't understand what 'Start' & 'Over' are for here - I guess the |
| 50 | idea was to integrate with other calendars, e.g. a critical one being |
| 51 | the reporting of volunteer hours (i.e. feeding into |
| 52 | hrm_programme_hours) |
| 53 | - I would hide the fields from the UI until implemented (can keep the |
| 54 | fields in code, perhaps commented out with an @ToDo (I'd also rename |
| 55 | 'Over' as 'End' to be consistent with other usages.) |
| 56 | * Does the People list on the left-hand side get filtered for people |
| 57 | already-assigned? |
| 58 | * The 'Roles' menu link is incorrect (points to the same as 'People') |
| 59 | * Like that list, I would have the HRM controllers that you use |
| 60 | available from the Roster module (keep users within your module when |
| 61 | accessing these options, which may require moving functions to modules |
| 62 | & then calling from the 2 controllers) |
| 63 | * The code could use some style improvements: PEP8 spacing & Eden |
| 64 | comment lines between functions |