#django

On my site I have a menu item that is a list of model objects, what is the recommended way to make that list available on all pages?

On my site I have a menu item that is a list of model objects, what is the recommended way to make that list available on all pages?

I'm trying to manage users from admin and I don't see what this documentation is referring to. https://docs.djangoproject.com/en/dev/topics/au... I was not asked to create user + password before having complete record, I was not able to change password, it gives me a plaintext field not a represntation of type of storage details

so I'm exploring templates. Template inheritance in particular. Is there some common name for the "Default site template that everything extends by default", and if so, where can I edit it?

or rather, where can I get it for later editing

aarcane: its kinda up to you, most people will call it base or default

rideh, so what I'm worried about is individual app development. Should an individual app be able to pull in the site default template from it's own templates? or is there some other methodology here?

aarcane: from my experience (limited) it needs to be stand alone, people can override or change them as necessary

you can't predict what others will do, so provide a good example of how it can be used, let them change as needed

keep your logic in your models, mixins, etc. keep it out of views /templates to facilitate this

mixins?

aarcane: Typically when you install a 3rd party app, you'll either not include templates with it, or you'l include some very basic ones as a template tutorial for the app, with expectations that they'll be overridden by the user.

jaddison: thanks you said it much better

jaddison, that makes good sense.

i keep wanting to go back to using pyjade, but it is so bad to debug

so I'm finishing with my basic application example, Polls. A thought keeps occuring to me, if I was developing this, by default, I would want the index page in a sidebar of some sort, not it's own page, and I would want it on like.. every page by default. How would I go about doing that?

writing templates long hand sucks..

just a keyword for the documentation would be a good answer

aarcane: https://docs.djangoproject.com/en/1.5/topics/te...

rideh, I was already reading that page, and from there I could put a STATIC list of polls in a sidebar. What I want is to know how to do something like adding {% include 'polls:index' %} from a template to include a view from elsewhere, or otherwise get a dynamically generated list of polls on every page without having to add polls code to each view.

aarcane: I'd make a base template that has {% block sidebar %} and {% block content %}

aarcane: where sidebar is the code for rendering your polls index, thus would be generated on every page

aarcane: within the {% block sidebar %} you can leave the polsl index code, but from any given template that inherits this can overwrite it with something different if need be

rideh, if you've done the tutorial recently you know that the polls tutorial uses generic views... I think I found a one-line reference explaining what I want, I think what I'm looking for is "Custom template tags"

aarcane: sorry it's been quite a while since i'd gone through the tuts

When creating a 3rd party app, it's sometimes good practice to create a templates/app_name/base.html that extends templates/base.html - that way, it makes it easier for users to pull in your distributed templates simply by overriding your templates/app_name/base.html. It really depends on your situation.