The admin's fine of course, because it has javascript. But then when using django-filter in django-rest-framework or anything else that relies on django defaults then the party is over and the fight for usability begins again.
I feel that in a majority of the cases, it's not for something I want, but for something that's just usable. In these cases, I am frustrated because this blocks me from moving on to building something I want. It doesn't make sense *for me*, to have to override all form classes in the world, to replace something that's not usable by something that's usable. If I'm overloading something, it should be to "add value", not to "make it usable", in my personal, own opinion. My point is indeed not necessarily to bake new fields in the core. We should be able to share as much as possible with upstream Django ! But at least I need hooks in Django code to be able to override the defaults form fields. And everything I proposed on django-dev since the fall of DAL v2 had a defect or another that just prevented it from going forward. I'm not saying they should have accepted my proposals, I'm just saying that I want to be able to iterate on something, whatever that is. And it has to be done outside of Django, based on my understanding of Django processes. It has to be accepted first, before it can be deployed. But I need to deploy something and iterate, before I can convince that it is acceptable :P About jquery autocomplete light there is a PoC to use JAL on DAL rather than select2: https://github.com/yourlabs/django-autocomplete-light/pull/749 I prefer JAL to select2 myself, because of the server side rendering and simplicity... But we'll have to stick with select2 until we find money to continue cover JAL with unit tests. Best, Jamesie <3 -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAC6Op1878DfGxN2_D3m1NCf8zR%3DU%2BY83gGuuW--5ENRz3XqrBg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
