On 26 août, 19:33, Steve Holden wrote:
> As long as you acknowledge it as an ugly hack I suspect your reputation
> will survive ...
>
+1 !-)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@g
On 26 août, 17:30, Uwe Schuerkamp wrote:
>
> Hello Bruno,
>
> thanks for your answer. I'm already using a custom context_processor
> (yay! ;-), so I'll follow that suggestion, too. I've tried wrapping my
> head around the process_view function, but I'm not exactly clear on
> how it works just yet.
On 26 août, 18:55, Aspontus wrote:
> Hi.
> If I understand your problem correctly, you are looking for a way to
> capture different optional parameters from the url, to use them in
> further url construction.
> Why not use /country/de/district/hf/observation/add/ with entries
Why add unneeded
On 8/26/2010 11:30 AM, Uwe Schuerkamp wrote:
[...]
> It's probably not a good idea to have google groups archive this ugly
> hack with my name on it, but right now it seems to do the job nicely.
> Storing the data in the request object also seems like a great idea,
> I'll certainly look into that!
Hi.
If I understand your problem correctly, you are looking for a way to
capture different optional parameters from the url, to use them in
further url construction.
Why not use /country/de/district/hf/observation/add/ with entries in
urlconf like:
urlpatterns += patterns('some.app.views',
url(
On 26 Aug., 17:08, bruno desthuilliers
wrote:
> > So would it be possible to access the request.path property from
> > within a custom template tag?
>
> Of course, as long as
> 1/ you pass it explicitely or
> 2/ the request.path is available in the context passed to the tag's
> render() method.
>
On 26 août, 16:43, Uwe Schuerkamp wrote:
> On 26 Aug., 15:56, joconnell wrote:
>
> > Hi Uwe,
>
> > You might be able to leverage the 'url' template tag which comes with
> > django?
>
> Hi John & Bruno,
>
> thanks for your answer.
>
> I've looked at the url tag, but sadly it doesn't help me with
>
On 26 Aug., 15:56, joconnell wrote:
> Hi Uwe,
>
> You might be able to leverage the 'url' template tag which comes with
> django?
>
Hi John & Bruno,
thanks for your answer.
I've looked at the url tag, but sadly it doesn't help me with
customizing the url's in the left navigation. The idea is th
Hi Uwe,
You might be able to leverage the 'url' template tag which comes with
django?
e.g. For the 'add observation' example above, if you pass in the
country code as part of the context you return in your view(s), or
leverage middleware to automatically add it to every response based on
the requ
On 26 août, 13:27, Uwe Schuerkamp wrote:
> Thanks Bruno,
>
> I'll look into the custom template tags you mentioned.
Well, the way I see it you should first investigate the middleware
part - that's probably where you'll get the most relevant infos. The
templatetag part was mostly here to help wi
Thanks Bruno,
I'll look into the custom template tags you mentioned. I had no idea
when I started out with this project that I'd be knee deep into
advanced django after a couple of weeks ;-)
BTW, can you recommend the "pro django" book?
All the best & thanks again for your help,
Uwe
--
You rec
On 25 août, 23:40, Uwe Schuerkamp wrote:
> Hi folks,
>
> this posting sort of refers to my previous problem from last week as
> I'm still working on the birdwatcher's site. I cannot wrap my head
> around how to create intelligent navigation links from the current
> context or http request.
(snip
Hi folks,
this posting sort of refers to my previous problem from last week as
I'm still working on the birdwatcher's site. I cannot wrap my head
around how to create intelligent navigation links from the current
context or http request. For instance, if the user enters via the url
/de/observers/
13 matches
Mail list logo
