I think this discussion has reached its logical end as it often does.
With that I will end it the way all the other discussions have ended
^_^.
Write the integration framework for the Javascript library you like
and get community support for it.
If that support gets enough steam it will be considered for django
contrib inclusion.
The django core team has decided that they will not work on any core
integration with any specific library, and there are no standards
across libraries to do some sort of standard support (ala WSGI). What
this means is that the django userbase community must do this work to
prove its usefulness. A proof of concept is needed as we need to prove
that the decision to not integrate with javascript is wrong. Saying
its wrong and providing the same old reasons is not changing anything.
I personally hate the 'don't like it? write the code!' sentiment, but
sometimes its the only option left. This is one of those times.
-Doug
(NOTE: I do not speak for the django development team, I am not part
of that team. Opinions expressed are mine and mine alone, so please
keep all angry responses directed at me, as I am the only one who
deserves them.)
On Apr 12, 1:34 pm, "pcad" <[EMAIL PROTECTED]> wrote:
> > I like jQuery. You like mochikit. Others like YUI, or Prototype, or
> > Dojo. Who's right? Everybody. Nobody. It depends.
>
> I probably shouldn't have brought mochikit into it:) I like it, true
> enough, but I'd actually be happy to abandon it if there was some
> strong benefit like community involvement.
>
> You're right that picking a library is likely to be a matter of
> opinion, and therefore will likely cause a controversy. (Are
> javascript library wars anything like language wars?) But that
> doesn't mean it isn't worth it. If my little horse doesn't win the
> race I'm not exactly going to switch to J2EE/Rails/Pylons/<insert
> favorite project here>.
>
> If I don't like the library that gets chosen I can always download my
> own code. The django code base already comes with js for the admin
> interface and I've never once looked at (no offense to the devs, it
> just seems tied into the admin interface).
>
> There's an opportunity here to build the community as well as catalyze
> some framework cross-pollination. Now you might not want to hitch
> your wagon to a dying horse (I don't), but there are some pretty
> interesting projects out there. I'm sure they would welcome a bunch
> of energetic pythonistas making their code more formidable.
>
> Just agreeing on an unofficial library might start something
> interesting. There are already two votes for jQuery.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
