On 6/4/07, Ittay Dror <[EMAIL PROTECTED]> wrote:
>
>
> On Jun 3, 9:50 am, Nicola Larosa <[EMAIL PROTECTED]> wrote:
> > IttayDror wrote:
> > > I was wondering if anyone has thought about makingdjango'stemplating
> > > system more in the concepts of wicket (there are other such templating
> > > engines, this is the one i've used).
> >
> > That's not going to happen, as you know by now. However, using any other
>
> That's a shame. I like Python very much, but I don't want to inforce
> it on my web designer. As I wrote, we transitioned from JSP to Wicket:
> our web designer was very happy (or is making people happy just a
> rails thing ;-) ), and we could separate files between the developers
> and the designer. (btw, he was happy since he could see his
> 'code' (html) clearly and could edit it in his editor)
>

One of the explicit design goals of Django's template system is to
_not_ be a programming language - Python or otherwise. The other
explicit goal is to separate the design of a page from the content of
the page, so that your designer doesn't have to become a programmer to
work on your site. The view programmer develops the view (in python),
which establishes the data that is available for display; the designer
works on HTML pages (using the template syntax) to produce HTML that
puts that data into visual form.

Using your suggestion, it is true to say that the designer doesn't
need to learn Python. However, the view programmer _would_ be
providing HTML chunks for use in the template - which means that the
designer would need to learn HTML, constraining the options available
to the designer, and you would end up with very poor separation of
design from view logic.

Like I said before - Django templates are the way they are for a very
good reason, and they're not going to change substantially. However,
if you don't like our reasons, feel free to use something else. Django
won't stop you.

Yours,
Russ Magee %-)

--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to