ka-lite
ka-lite copied to clipboard
Clean interaction between facility and control_panel apps
Currently I'm a bit unclear on the interactions. In general, I hope we could have the follow app and inter-app structures:
- Apps can stand alone. In this case,
Facility
app should be able to create/edit users, create/edit groups, create/edit facilities. - Apps that want to modify other apps behavior import the other app, then override behaviors:
- Import view functions and override things like redirects.
- Override templates by adding a template with the same name to the overriding app's
templates
directory, then strategically setting the order ofINSTALLED_APPS
so the override is selected.
For the facility
/ control_panel
interaction, I am most looking at the use of add/edit forms across the two apps.
@rtibbles your feedback on this one would be appreciated. I'm happy to do refactoring, but don't want to refactor things in ways that wind up being confusing.
I think it makes sense to have view code in facility that allows for the adding/editing of all facility models. Any additional functionality can then be added after being imported into control_panel for enhancement.
Refactoring = @bcipolli
0.13.