Inline. "hugo" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Just some thoughts from me on this: it would make much more sense to > address the whole Ajax stuff from a practical point - start adding > stuff to the admin that needs Ajax or at least makes good use of it. > Then we can see what we really need in Django for Ajax support.
+1. > _Then_ we can discuss which of those emitting patterns we want to add > to Django. Django started out as an "extracted" framework (in contrast > to some "designed" framework, where the framework is first and the > application is next), I think we should do the same for any Ajax+Django > parts. +1. > A good start (and one that - at least I would think - many would > applaud) would be to add support for search-suggestion to the Django > admin search field. Another that comes to mind would be changing the > two-column-stuff in the admin (used for permissions for example) to > make use of Drag-n-Drop. One could be to revive the partly existing > drag-n-drop support for element ordering. Hmm. +1. > Don't get me wrong: I am not completely against Ajax or JavaScript. But > I am a bit wary of yet another approach to the problem from the "let's > design a Ajax+Something framework" side, I've seen that far too often > and far too often (even in this project already) it didn't really reach > a point of useabliity or at least common agreement. Let's try something > different and first provide problem solutions, and _then_ extract a > framework out of them. At this point I suspect you didn't actually read the post. I spent 1/3 of it discussing autosuggest widget - the one, which should be used "to add support for search-suggestion to the Django admin search field". The list of widgets was derived from my personal needs with Django, not from "it's nice to have something". It includes drag-and drop for reordering and selection. There is no attempt at "let's design a Ajax+Something framework". Actually there is no design at all --- just extracted pieces. Do you want to see it in code? I want to see it in code too. But I am just a one-army man with plenty of projects coming down the pipe. I want to manage my priorities and my time. That's why I asked for constructive criticism, yays/nays, and so on. I understand that by saying "let's try something different and first provide problem solutions" you have a lot to say about problems (problem analysis would be nice at this point) and their solutions (some proposal would be nice at that point). Let's see your thoughts on that "and _then_ extract a framework out of them", if it is possible. Thanks, Eugene
