> It includes ajax file upload which every user expects in the modern web which > seems to be the feature which defines feature-completion of a UI framework, > compared to what HTML offers out of the box. Bandwagon logical fallacy (“every user expects”)
In my project, I have no need for file upload. And I have no need for it in the foreseeable future, and, as such, I do not expect my framework to be able to handle it. I’m neither supportive nor opposed to the idea of changing Django forms, but please avoid logical fallacies in supporting your position. From: [email protected] [mailto:[email protected]] On Behalf Of Jamesie Pic Sent: Saturday, February 3, 2018 6:36 PM To: [email protected] Subject: Re: DEP Pre-posal: Re-Designing Django Forms On Thu, Feb 1, 2018 at 12:46 PM, Marc Tamlyn <[email protected]<mailto:[email protected]>> wrote: > This is a huge project to achieve everything you mentioned in your email, and > it has implications across a large number of Django packages (not least the > admin). I don't want to discourage you, but don't underestimate how much work > it would be to get a good replacement for forms for the modern web. Perhaps we should just be able to swap Forms with WTForms or another python library and bake in ElementUI, even if that means replacing template_name with vue_name in the view generic class, but if we're talking about "modern web" then perhaps it's time for npm to become a first class citizen. > Your next steps should be to research, spec and potentially write a DEP. In my recent research it seemed ElementUI the most feature complete UI. It includes ajax file upload which every user expects in the modern web which seems to be the feature which defines feature-completion of a UI framework, compared to what HTML offers out of the box. Thanks a lot for doing something about this Robert, forms in django definitely needs a major refactoring sprint, typically remove the field/widget layer and rely on one level inheritance that will help a lot for example with material design which displays field.name<http://field.name> inside the widget, not possible with current object design. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAC6Op1_ESqUA6tUwQxwgastH4XzQ%3D-PBybtq__2yWEuc0OH4BA%40mail.gmail.com<https://groups.google.com/d/msgid/django-developers/CAC6Op1_ESqUA6tUwQxwgastH4XzQ%3D-PBybtq__2yWEuc0OH4BA%40mail.gmail.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c44115b589e94fa0b6da27854b114332%40ISS1.ISS.LOCAL. For more options, visit https://groups.google.com/d/optout.
