hugo wrote:
> Hi,
>
>
>>Hence, I plead with the proponents of "Ajax support:" Please >show
>>concrete examples of what you want. Enlighten us.
>
>
> Actually the only thing I can think of that would be good if django had
> it, would be a REST style API to access model stuff that automatically
> will be returned in JSON format. That would allow JavaScript code to do
> easy database queries without requiring the programmer to write those
> views himself.
>
> Most AJAX stuff is just stuff built on database queries anyway (like
> the google suggest feature nowadays seen as lifesearch in projects -
> just a query directly run from JavaScript).
>
> But I am not exactly a proponent of "AJAX support in Django", as I
> already use AJAX with Django quite happily and can't see much (beside
> the above thingy) that could be provided in django core ;-)
>
> bye, Georg
>
>
What I don't understand about this position is:
a) You are using AJAX
b) You find it useful
c) You are using a toolkit
Thats great.
If we want AJAX functionality in the admin or comments apps, do we ban
using a toolkit so as not to express a preference? Why should the
bundled apps not be allowed to follow best practices? The fact that
something is bundled doesn't mean people have to use it. But it does
mean that *we* can't use it for bundled apps. Whether this bundling
leads to other people using it is up to them. In practice, people are
far more likely to use the bundled kit. Is this really a huge downside?
The other problem : if this discussion fizzles out into a "oh, AJAX is
so simple, its just http requests, I don't know what the fuss is about,
{% smart_arse_DHTML_comment %}" as it always seems to, it just leaves
users with uncertainty. Users will assume that at some point in the
future we will decide to bundle a kit ( they will assume this because
all of our competitors do.)
So the users will think
1) Django isn't as "good" as other frameworks
2) I don't know what toolkit to use. Whichever one I pick, at some point
in the future Django will pick a different one, and I will either be
screwed or missing out on automatic functionality. Maybe I should just
go with something more "complete".
So lets not pretend that there is zero cost to *not* picking something.
Users don't like uncertainty.
------------
Another thing that I can definitely see being an AJAXian desire in
django core : FormFields output text directly, rather than an AST. This
does not fit in with some JSON oriented approaches. An AST could be
converted to HTML or JSON instead. I personally don't use this approach,
but it does seem a legitimate concern.
Robert
