Dear Andréas, During the past decade, I have fought that model fields do not have usable form fields out of the box.
"Django doesn't want to couple a JS framework", is what I remember from discussions. For me, having JS enabled form fields does not mean **removing** support for pure-HTML form fields, so, nobody would be actually "coupled with a JS framework". And, supporting one JS framework doesn't mean Django couldn't support other framework neither. I'd like to try a Django fork that LOVES javascript and out of the box experience. Currently, the philosophy in Django is "if it can be in an app then it should be in an app", which opposes what "improving ootb experience" means for me. Also, I'd like it to make it easier for newbies to install Django projects, I've posted about this in a thread about DJANGO_SETTINGS_FILE on django-dev. And of course, I'd like a fork that's easy to contribute to, iterate with, so that features can mature outside of Django before being proposed upstream. I'm up for helping others on their features too of course ;) 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. 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/CAC6Op1_TS58kQUnDv0_3vXtF%3DbnsUaqtOe7zq2f8kKe4XBsssw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
