On 29-6-2012 5:45, Ryan Nowakowski wrote:
> Or a custom template context processor that adds gigs to every request
> context.
Or just use an iframe in your template that loads the gigs rendering view.
Iframe bad, yes, and all that, but the simplest solution in this case if
your layout can handle it.
A variation is to have them loaded by Ajax, with the drawback that
javascript-disabled browsers miss content. As I browse with noscript all
the time, this isn't a big problem. If I get to a page I'm interested
in, I will grant the domain the privileges in an instant.
Point being, refactoring code duplication isn't limited to the django layer.
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment