Opened 18 years ago
Closed 17 years ago
#3559 closed (wontfix)
Should have official simple AJAX documentation
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Design decision needed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I've seen all the reasons why Django doesn't have a plug-n-play javascript framework, and agree. However, this appears to give Django some sort of anti-javascript/AJAX reputation and drives people away from Django (see e.g. does Django have an AJAX plan?). Given that this sort of thing is a web2.0ey buzzword, I can see this being used as a deciding factor in Dilbert-esque management meetings.
Whilst there are good reasons not to tie into a specific framework (e.g. Ubernostrums infamous post), there is plenty that Django does to make it easy to do AJAX-y things.
This should be documented fairly briefly, but *prominently* to correct these misconceptions, and can incorporate info from/link to the many wiki pages (e.g. XML-RPC) or blog posts (e.g. another b-list post) where people can find more information.
Change History (4)
comment:1 by , 18 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
comment:2 by , 18 years ago
Triage Stage: | Design decision needed → Unreviewed |
---|
comment:3 by , 18 years ago
Triage Stage: | Unreviewed → Design decision needed |
---|
Sounds good, what does core think?
comment:4 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I guess I don't see much point to this because it's not really Django-specific; Django's agnosticism means that you just write what you'd write anyway.
Just to clarify a bit - I'm not saying that we should implement a javascript framework, or write an ajax-and-django tutorial, but more answer this as a sort of FAQ, by justifying why we don't incorporate a framework, mention why this isn't an issue, direct the reader to the serialisers docs, and whatever collection of tutorials we can find that others have written.