Inline. "Wilson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > I think Dojo looks great. Their rich text editor demo looks like it's > designed to plug in to the Django admin :)
:) I am thinking to switch from TinyMCE to Dojo Rich Editor on my web sites. > Before we get too far into the "which Ajax framework should Django use" > discussion, I think it's important to lay the groundwork first. > > It seems to me that the goal of any Ajax support in Django should be to > make it easier to integrate with any Ajax framework. If there is a > default Ajax framework coupled with Django (it may just be a matter of > which one is bundled and documented) it should be at least as easy to > use another framework (or frameworks) as it is to use other template > systems. Loose coupling, sensible defaults, etc. +1. I would prefer Ajax-related additions to be a separate subsystem (application, middleware, bunch of related classes, and so on), which should be used only when app developer says so. > So the real productive question at this stage isn't "which Ajax > framework", it's "how can Django make Ajax easier for app developers." Hear! Hear! > At that point, what framework you use or whether you roll your own is > up to you. Right. I don't think that Django should have "AJAX in the core". Simple no-nonsense HTML-only web side should be possible. I do think Admin would gain a lot in terms of usability from going Ajax. I do think that reinventing wheels is not necessary, when there are true and tried libraries, which are supported and enhanced without our direct involvement. Thanks, Eugene
