Merge lp:~danilo/summit/private-attendees into lp:summit
| Status: | Merged |
|---|---|
| Approved by: | Chris Johnston on 2012-01-25 |
| Approved revision: | 271 |
| Merged at revision: | 271 |
| Proposed branch: | lp:~danilo/summit/private-attendees |
| Merge into: | lp:summit |
| Diff against target: |
155 lines (+89/-14) 5 files modified
summit/schedule/forms.py (+73/-10) summit/schedule/templates/schedule/create_private.html (+7/-0) summit/schedule/templates/schedule/edit_private.html (+7/-0) summit/schedule/tests.py (+1/-2) summit/schedule/views.py (+1/-2) |
| To merge this branch: | bzr merge lp:~danilo/summit/private-attendees |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Chris Johnston | 2012-01-25 | Approve on 2012-01-25 | |
|
Review via email:
|
|||
Commit Message
Makes it possible for the creator of a private meeting to add required participants.
Description of the Change
WARNING: no tests due to time being limited!
Add ability to private meetings page to add attendees directly.
It turns out formsets do not really support dealing with many-to-many relations, so I turned back to the approach I planned from the get-go: override save() method to take special consideration for the 'participants' field.
For better usability, I am also using multiple-checkboxes widget instead of multi-select box, because it allows at least easy searching using one's browser's built-in search in a long list of ~200 registered people.
We should definitely display meeting attendants on the private meeting page as well, but I'd rather do that as a separate branch.
