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
> 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
On 4/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> pcad, there's some good points there, and maybe many of us could share
> more code showing how we've integrated whatever JS toolkit with
> Django. But I like the agnostic stand. They give the tools to connect
> easily. HOW you connect
pcad, there's some good points there, and maybe many of us could share
more code showing how we've integrated whatever JS toolkit with
Django. But I like the agnostic stand. They give the tools to connect
easily. HOW you connect is up to you.
I like jQuery. You like mochikit. Others like YUI, or
> thread when I first came to Django. In hindsight, it was pure
> inability to write the javascript myself, and reluctance to properly
> learn javascript. In the end I've seen that writing javascript
> manually results in much cleaner html output, using less code and it
> sometimes just performs
I think that most people that ask for "ajax integration" want to see
javascript helpers, as seen in many other frameworks. They're looking
for things like for example {% auto_complete_tag .. params ..%}; wich
would render an input box with the necessary javascript (inline..)
that makes it
On Apr 10, 11:39 am, "Todd O'Bryan" <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-04-10 at 18:11 +, Steve Bergman wrote:
> > But Django definitely has a preferred ORM and a preferred templating
> > engine. Why be so set on complete agnosticism when it comes to
> > javascript?
>
> I agree. I
On 4/11/07, Adam Findley <[EMAIL PROTECTED]> wrote:
>
> I like the idea that Django is AJAX implementation agnostic the same way
> it is agnostic to the database you prefer to back your project (if any),
> but, is there any work being done to create something in contrib to
> facilitate working
On 10-Apr-07, at 11:41 PM, Steve Bergman wrote:
> But Django definitely has a preferred ORM and a preferred templating
> engine. Why be so set on complete agnosticism when it comes to
> javascript?
then, to complete your analogy, they would have to write and maintain
their own javascript
2007/4/10, James Bennett <[EMAIL PROTECTED]>:
>
>
> Again, it's not terribly hard to write views which return JSON or XML;
> integration with form widgets, etc. requires binding to a specific JS
> library or rolling our own, and that's not going to happen.
>
With Django is terribly easy to do
On 4/10/07, Steve Bergman <[EMAIL PROTECTED]> wrote:
> Even after the developer decides upon a javascript library to use,
> there is still a lot of boilerplate involved to do common things like
> populating one widget based upon what the user selects in another
> widget. I often need to
On Tue, 2007-04-10 at 18:11 +, Steve Bergman wrote:
> But Django definitely has a preferred ORM and a preferred templating
> engine. Why be so set on complete agnosticism when it comes to
> javascript?
>
I agree. I don't have time to weigh the benefits of various libraries.
As someone
On 4/10/07, Steve Bergman <[EMAIL PROTECTED]> wrote:
> And, OK, I'll fess up and say that I want to think in python and not
> have to switch gears back and forth between python and javascript. ;-)
To me, for all the other arguments people make, this is the real
issue: wanting to avoid writing
To me, that does not seem very DRY.
Even after the developer decides upon a javascript library to use,
there is still a lot of boilerplate involved to do common things like
populating one widget based upon what the user selects in another
widget. I often need to populate one widget based upon
James Bennett wrote:
> On 4/10/07, erdong ma <[EMAIL PROTECTED]> wrote:
>> I do not know if a decision has been made on the ajax framework in 1.0.
>
> Django will not bundle any JavaScript library or provide integration
> hooks with any specific library; Django will continue to make it easy
> to
On 4/10/07, erdong ma <[EMAIL PROTECTED]> wrote:
> I do not know if a decision has been made on the ajax framework in 1.0.
Django will not bundle any JavaScript library or provide integration
hooks with any specific library; Django will continue to make it easy
to receive AJAX requests and send
Hi Erdong,
If you do a simple search for "AJAX" on this group you'll find the answer
you're looking for, in brief: Django **will not** advocate for a specific
ajax framework/library it provides useful tools to ease your development i.e.
Serializers but as jacob sais a few days ago: "why should you
I do not know if a decision has been made on the ajax framework in 1.0.
Anyone knows some message about this.
By the way, how about the Eclipse + pydev comparing with the Wing IDE?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
18 matches
Mail list logo
