Re: FAQ on Model-View-Controller

Dan, please offer a pull request if you are able. On Saturday, August 8, 2015 at 12:03:06 PM UTC-4, Dan S wrote: > > Hello Aymeric, > > I apologize for using an aggressive tone, it is not my intent to insult > anyone, just to request that content be updated. xkcd/386 on the other > hand makes

Re: FAQ on Model-View-Controller

Hi Dan, On 8 août 2015, at 18:03, Dan S wrote: > So I humbly suggest that the wording of the FAQ be adjusted to make clear > that the "meaning" of V and C are not debatable, that templates and > template-feeding code always serve the purpose of Viewing the model, and that > Controller code can

Re: FAQ on Model-View-Controller

Hello Aymeric, I apologize for using an aggressive tone, it is not my intent to insult anyone, just to request that content be updated. xkcd/386 on the other hand makes it personal, referring to some*one*, not some*thing* :-) I suppose I intended to say that MVC is not defined within the cont

Re: FAQ on Model-View-Controller

Hello Dan, Depending on the size and complexity of a Django project, there are two ways to implement MVC. (I’m talking of a traditional Django project, not Django-as-an-API-for-a-JS-app.) 1) Small project: the straightforward way M = models.py V = template.html C = thick views.py: most of the

FAQ on Model-View-Controller

The Django FAQ says: *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?*¶