| 6 | | [[Image(architecture.png)]] |
| | 5 | [[Image(architecture.png, 200)]] |
| | 6 | |
| | 7 | However, we want to use the DjangoFramework, in which the "Controller" is [http://www.djangoproject.com/documentation/faq/#django-appears-to-be-a-mvc-framework-but-you-call-the-controller-the-view-and-the-view-the-template-how-come-you-don-t-use-the-standard-names somewhat called "View"], which is arguable but quite coherent : a View, in Django, determines what to render, not how to render it. This is a subtle difference. Anyway the most important point is to properly separate the data from the various rendering routines and modules. |
| | 8 | |
| | 9 | So here is the UML class diagram, where you'll find views and the model, no controller ([source:trunk/doc/devel/class_diagram.uml source] edited with [http://argouml.tigris.org/ ArgoUML]) : |
| | 10 | |
| | 11 | |
| | 12 | |
| | 13 | |
| | 14 | |
| | 15 | |