On 8/19/06, simonbun <[EMAIL PROTECTED]> wrote: > I'm well aware that its no problem to use ajax right now by using any > JS toolkit. My point was that it seems somewhat wasteful to have custom > JS scripts for the admin generator, and then using a JS toolkit that > does the same thing.
I submitted a partial porting of the admin JS to the Dojo toolkit a while back, but honestly I don't mind one way or the other if it ever goes in. If we decide to do real AJAX stuff in the admin app, then we'll probably have to pick a toolkit for it and bundle that with the admin app. For now, "waste" strikes me as a non-issue -- it's like saying that because the admin app uses XHTML 1.0 Strict, it'd be "wasteful" for someone to have their public-facing templates be HTML 4.01 Transitional. What the admin app does or doesn't do shouldn't have any bearing on the techniques you choose for the public part of an application. > Thats not the issue. Everyone can make their own choise perfectly well, > but if a "blessed" toolkit is chosen, more people are swimming in the > same direction. Wich would make it easier to bounce off of each others' > ideas & code, and maybe to help others that are stuck on something. To > me thats a benefit, to others maybe a limitation. The problem here is that, well, there's no such thing as "swimming in the same direction" -- to get that to work, there would have to be a one-size-fits-all JS toolkit out there, and there just isn't and never will be such a thing. But if somebody wants a "blessing", then here's a blessing that carries whatever weight people attach to my rambling opinions: The official JavaScript toolkit of the Django web framework is the one that best suits what you want to do with it. The BDFL bless you and keep you, etc. > How is that a self-fulfilling prophecy? I was just saying that choosing > a particular toolkit will not get in the way of django developers that > choose not to use it. Much like the current JS doesn't get in the way. Time and time and time again we've seen people who -- literally -- would take a "bundled" toolkit as a blanket statement of "use this, and nothing else". That's not how we roll. And the opposite statement could be made in response to your argument -- *not* choosing a particular toolkit doesn't get in anyone's way, either. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
