On Sat, 2007-10-20 at 22:40 -0700, Leo Shklovskii wrote:
> Does anyone have any thoughts on this? is there a recommended way to lay
> out the templates on a per-application basis? does it make sense to
> change either of the two defaults to be consistent with each other?
>
> --
> --Leo
>
> Leo
foo/templates/foo/bar.html
foo/templates/foo/bar_list.html
This is the way I've been doing it (app/templates/app/model.html). It works
well when you want to re-use your apps to make sure template names don't
conflict with other apps.
On 10/20/07, Leo Shklovskii <[EMAIL PROTECTED]> wrote:
>
>
> D
Does anyone have any thoughts on this? is there a recommended way to lay
out the templates on a per-application basis? does it make sense to
change either of the two defaults to be consistent with each other?
--
--Leo
Leo Shklovskii wrote:
> I've got a question about the templates that the gen
I've got a question about the templates that the generic views load.
I have a app (named 'foo' in this example) that has its templates in a
templates folder to work with
django.template.loaders.app_directories.load_template_source.
so:
foo/templates/bar.html
foo/templates/bar_list.html
Howeve
4 matches
Mail list logo