On Fri, Apr 19, 2013, Russell Keith-Magee <[email protected]> wrote:
>> So should the advice be to treat message template output as a site-wide >> feature, or as an application-related feature? > >I'm not sure I see why this is something that Django needs to state an >opinion on. Django deals with the issue at the server side - making sure >that messages can be captured, stored and retrieved as necessary. The >decision of how to display those messages really is up to the end user. I >can see legitimate reasons why you'd want to take both approaches you >describe, and the decision to use one or the other really depends on the >templates and visual layout of the site under discussion. Thanks, that's useful. When the question came up, one opinion was that messages are site-wide, so displaying them in application-specific templates is incorrect: <https://github.com/evildmp/django-form-designer/commit/c8a38458734cc1e8c0c6433c38516fa812c6a92b#commitcomment-3036344> Even if Django's advice is that it doesn't really matter where messages templates are as long as they behave nicely, that would be useful advice. Daniele -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
