Changes between Version 4 and Version 5 of GlobalArchitecture


Ignore:
Timestamp:
Mar 26, 2007 10:03:00 PM (7 years ago)
Author:
olivier
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GlobalArchitecture

    v4 v5  
    33The basic idea is to follow the ModelViewController, as in the initial design proposal below ([source:trunk/doc/devel/architecture.svg Inkscape SVG source]) : 
    44 
    5 [[Image(architecture.png, 200)]] 
     5[[Image(architecture.png, 300)]] 
    66 
    77However, 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. 
     
    99So 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]) : 
    1010 
     11[[Image(class_diagram.png, 300)]] 
    1112 
    1213 
    1314 
    1415 
    15