I know I'm not a core dev but I do have two cents. I'm not really in favor of overthinking this too much--I think a satisfactory replacement for raw_id_fields is good enough (adequately encompasses all the features). I know there are a lot of mature projects out there when it comes to AjaxFields and I don't think its up to django.contrib.admin to compete with them--they are there to use and can easily be integrated into admin for those who require advanced features.
As for the big picture of admin in 5 years, its certainly a good question but I'm not sure that its 'the question to be asked first of all'. Overthinking like this stalls tickets, sometimes indefinitely. Please don't think I'm trying to hinder discussion. I just don't think making an absolute answer to that discussion a contingency of this called-for feature. -Steve On Oct 1, 3:42 am, "burc...@gmail.com" <burc...@gmail.com> wrote: > Hi everyone, > > Anyway, I'd like to see notes from core devs regarding adding such > feature to Admin interface (so please don't say -1 if you think it's > just not mature enough!). > > Or maybe all interested parties should work on some kind of > django-admin-extensions instead of improving admin itself. > > Actually, it seems there is still no consensus in the django community > of what ideal admin interface should look like. > It's very controversial question! > I remember django core devs repeatedly said that django.contrib.admin > should be simple, and they intends it should be useful only for few > use-cases like observing your data, adding at most few initial model > instances, editing users and permissions, and being example of how to > (not) create reusable django application with UI, and how to create > poll application with no use of db explorer like phpmyadmin. > > Different people tried to say many times that admin instead should be > extensible and have all sort of features to be really useful. > > How do you see django admin in 5 years? This is the question to be > asked first of all. > > Personally, I see django admin completely outside of django project in > 5 years, like django debug toolbar and the rest, and I'd say, django > core team time should use their time to review and apply patches, fix > bugs and add new features to django itself, so admin development > should be stopped, admin docs must contain: "admin app is not much > useful -- we just don't have enough time to add features into it, and > we don't think we should do this -- but it can be used as an example > for django beginners of how (not) to do reusable django applications". > > > > > > On Fri, Oct 1, 2010 at 5:45 AM, tyrion-mx <tyrion...@gmail.com> wrote: > > I've tried implementing Autocomplete for the admin using jQuery (new) > > Autocomplete, > > here's the code:http://bitbucket.org/tyrion/django > > and here's a live demo (without css for the autocomplete, so it looks > > kinda ugly):http://djangoac.tyrion.mx/admin/login with test/test. > > > Let me know what you think about it. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django developers" group. > > To post to this group, send email to django-develop...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-developers+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/django-developers?hl=en. > > -- > Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, > MSN: bu...@live.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
