Robert Wittams wrote:
> Sorry, I just can not work out what on earth you are actually trying to
> achieve - too many instances of the word 'generic'... A concrete
> example would be best.
Robert,
Sorry, I guess I wasn't communicating very clearly.
What I want is something like the {% include %
Sorry, I just can not work out what on earth you are actually trying to
achieve - too many instances of the word 'generic'... A concrete
example would be best.
At risk of hijacking the thread, I've been struggling with something
similar (if I understand patrick correctly) Basically, I've been trying
to come up with a way of including re-usable 'pagelets' or
sub-templates into a parent template that are rendered with their own
local context generated by g
Hmmm, looking at ticket #925, I think I prefer that solution - never
mind, just ignore me.
I'm a little late to this, but it should be noted that it's not
currently impossible to make the request available to the context, just
a little messy. I wrote the following middleware which does it (forgive
the rotten code - it was just a proof of concept)
from django.core.extensions import Djan
Hi,
I just commited two patches that implement JavaScript translation based
on my proposal to Django. I added translations to the date and time
pickers in the admin and added the necessary tags and references to the
admin app.
If you want to create an empty translation file for JavaScript, you
j
