?python,???asii
--~--~-~--~~~---~--~~
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,
2007/5/30, Panos Laganakos <[EMAIL PROTECTED]>:
>
> direct_to_template sounds like a nice way to handle the index page
> serving.
>
> But how can it be fed the dynamic content of one or more apps to
> display? Not sure how it's supposed to be done
> through "template tags" as Michel mentioned.
direct_to_template sounds like a nice way to handle the index page
serving.
But how can it be fed the dynamic content of one or more apps to
display? Not sure how it's supposed to be done
through "template tags" as Michel mentioned.
On May 24, 5:42 pm, Michel Thadeu Sabchuk <[EMAIL PROTECTED]>
Index page doesn't need a view. Generally it is a static page, if it
have some dynamic data, it access through template tags. So, I follow
this structure:
project/
project/templates/
project/templates/main/
project/templates/main/base.html
project/templates/main/index.html
2007/5/23, David Larlet <[EMAIL PROTECTED]>:
> Hi,
>
> I'm juste curious, where did you put your homepage view when you've
> got a project with a lot of apps? Is there a best practice here?
>
Thanks a lot for your answers!
David
--~--~-~--~~
> I'm juste curious, where did you put your homepage view when you've
> got a project with a lot of apps? Is there a best practice here?
An extra app? Man... Views do not *have* to reside inside some app.
Whenever I have some view not specific to some app, I create a module
for
> I'm juste curious, where did you put your homepage view when you've
> got a project with a lot of apps?
I create a django app called "site" and put my index view in there. I
also put any template tags and filters that will be used across the
project in t
> I usually make a home controller. Then I typically use an index
> action for the home page view.
This is normally what I do as well, I just define a view called
'index' somewhere and point r'^$' at it.
But this seems like a good place for me to ask a related question I've
often puzzled over:
> I usually make a home controller. Then I typically use an index
> action for the home page view.
This is normally what I do as well, I just define a view called
'index' somewhere and point r'^$' at it.
But this seems like a good place for me to ask a related question I've
often puzzled over:
> I usually make a home controller. Then I typically use an index
> action for the home page view.
This is normally what I do as well, I just define a view called
'index' somewhere and point r'^$' at it.
But this seems like a good place for me to ask a related question I've
often puzzled over:
On 5/23/07, David Larlet <[EMAIL PROTECTED]> wrote:
> I'm juste curious, where did you put your homepage view when you've
> got a project with a lot of apps? Is there a best practice here?
I usually make a home controller. Then I typically use an index
action for the home page view
wrote:
>
> Hi,
>
> I'm juste curious, where did you put your homepage view when you've
> got a project with a lot of apps? Is there a best practice here?
>
> Thanks,
> David
>
> >
>
--
Julio Nobrega - http://www.inerciasensorial.com.br
--~--~-~--~~
Hi,
I'm juste curious, where did you put your homepage view when you've
got a project with a lot of apps? Is there a best practice here?
Thanks,
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
13 matches
Mail list logo
