On Thu, Sep 27, 2012 at 10:59 AM, Javier Guerra Giraldez <[email protected]> wrote: > On Wed, Sep 26, 2012 at 5:50 PM, Lachlan Musicman <[email protected]> wrote: >> Do people have internal guidelines about when they make something a >> method on a model rather than a view function? > > if it's not a presentation thing, it probably goes in the model > > even some presentation things go there, like the __unicode__ method; > but nothing that assumes HTML
The more I think about it, the more it makes sense to put it in the model - then the Generic views can be used instead of having a long and ugly views.py filled with methods Hmmm L. > > -- > Javier > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- ...we look at the present day through a rear-view mirror. This is something Marshall McLuhan said back in the Sixties, when the world was in the grip of authentic-seeming future narratives. He said, “We look at the present through a rear-view mirror. We march backwards into the future.” http://www.warrenellis.com/?p=14314 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
