Hi,
I'm part of an erlang project called erlydtl which is a port of the
Django templating language.
We currently have a small dilemma about the "right way" to do
something and we thought it best to mirror what Django does.
The question is whether the definition of the document root should
change when evaluating includes.
For example, if I have template1 which includes path1/template2 then
should include statements within template2 be wrt. to the original
docroot *or* should everything be only relative to the one docroot.
I find it easier to relate to examples, so consider the following
directory structure of templates :
./template1
./path1/template2
./path2/template3
If template1 looks like this :
./template1 = '{%include "path1/temtlate2"%}'
Then if template2 wants to include template3 should it do this :
./path1/template2 = '{%include "../path2/template3"%}'
*or* should it do this :
./path1/template2 = '{%include "path2/template3"%}'
I tend to favor the latter because then the include path is
unambiguous since all includes are relative to the document root.
Which of these does Django implement? Or do you allow both? Or something else?
Thanks,
Colm
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
