I tried Django for creating a "configuration application". It seemed
pretty cool and reduced a lot of my work. I felt frustrated once ,
while creating two apps under one project , probably I missed few
obvious settings.
I tried creating two apps under 1 project.
This is what I assumed,
Django by
ashutux wrote:
> I tried creating two apps under 1 project.
> ...
> Now,I tried calling a template named "login.html" from second apps'
> view (second in the sense it was written at second position in
> "INSTALLED_APPS" ) but since "login.html" was also present under
> templates directory of first
kmh wrote:
> No. Rather, the convention is to put application specific templates in
> a subdirectory of the application templates folder with the same name
> as the application. That way you can refer to 'app1/login' and
> 'app2/login'. See:
>
> http://code.djangoproject.com/wiki/DosAndDontsFor
ashutux wrote:
> I find it a bit unconventional though.. Why have a separate apps_name
> ("apps1" for example) directory under template directory of the same
> app, since those templates are anyways going to be used by the only
> app?
> Has this convention appeared just because the way django code
Yes, I think what perhaps missing / not appropriate is Not much
discussion / documentation of what is "The Django Way."
We will have to wait until 1.0 I guess.
5 matches
Mail list logo
