I think you could do that (or something similar) with using template-
tags.
we´re having a sidebar on one of our django-sites where the user is
able to select the content (and position) she wants. since we don´t
know what´s going to be loaded when calling the view, we have to use
template-tags.
patrick
Am 18.09.2006 um 09:44 schrieb [EMAIL PROTECTED]:
>
> I am a happy but rather newbie user of django but one thing seems to
> rattle my chain :-). I've created a base template which includes
> several blocks which are overridden/inserted in the specific pages,
> but
> if the template is to use any context parameters I have to set
> these in
> ALL controller methods (or remember to call a generic template
> controller method also). I was looking for a way to include what seems
> to be quite close to be a portlet, basically it is just a way to
> include the output from another URL (being local or remote). I've
> started to write a portlet tag which would e.g. be an URL to another
> resource on the local server. To be more specific I'm doing this:
>
> BaseTemplate.html
> ----
> {% portlet /portlet/SomePortlet/ %}
>
> urls.py
> ----
> r'^portlet/SomePortlet/$','project.views.somePortlet'
>
> views.py
> ----
> def somePortlet(request):
> fetchData()
> return render_template(...)
>
> But I am not sure if there is a smarter way to do this and/or if this
> feature is already included in django somehow?
>
> regards / Lars Borup Jensen
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
