I'm a little bit confused about the discussion php vs django template at all.
The most of the posters here should take a look at the no. 1 php template engine: Smarty http://www.smarty.net/ Take the documentation of the template syntax, you will see that Smarty and Django Template are very similar, so similar that I wrote my first (not so simple) django template without even look at the docs of django. I'm not sure which system comes first [but I heared that it was smarty one time], django templates or smarty, but who ever was second knows the other one while planning its own solution. So a lot of php and python developers have a nearly identical handling of templates in there projects. On Aug 31, 12:36 am, Michael Schreifels <[EMAIL PROTECTED]> wrote: > If I wanted to work with PHP and didn't like the fact that it allowed > my designers to access PHP, I could certainly choose to use a template > language. But of course, it is going to involve overcoming a barrier > to implementation. Django templates works great for most people. For > those who it doesn't work for, they should be prepared to have to do > some extra work. Besides, for beginner's needs, what exactly is it > that Django templates doesn't work for? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
