James Bennett wrote:
On 8/2/06, gabor <[EMAIL PROTECTED]> wrote:
django does not force you to use the django-templating-system (you can
use myghty/zope-tal/whatever instead), but it clearly recommends the
django-templating-system, and that's the system which is the most
tested/streamlined/documented/developed.
I'm not convinced that the analogy holds; to me, officially endorsing
a particular JS toolkit would be like re-wiring the template system to
favor a particular version of HTML. Just as the choice of HTML or
XHTML and which version to use is best left to a case-by-case basis,
the choice of which JS toolkit to use is best left to a case-by-case
basis.
hmm.. probably this is the point where we disagree.. which is of course
not a bad thing.
maybe we should clarify what we mean by words like "endorse",
"recommend", "support" etc.
and also we're probably approaching this from the wrong end (or at least
i).
the real question probably is:
- what would we gain by having an 'official' _javascript_ library?
if the answer is "nothing" then we don't need an official js lib.
so, is there something that django could do to make ajax easier? (except
the server-get-get/post-and-responds-in-json)
gabor
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
