Hey Tom, My main goal is to improve the Django Form API interface for writing Python code for what Django has historically done: server-side rendered web pages. So any client-validation hooks I might provide would not be fully implemented integrations rather a more convenient integration. (I'm thinking of things like Parsley.js here.)
If I can happen to improve the API for interfacing with JS frameworks, then I'll be happy to do so, but that's honestly not even secondary in importance to me. However, my experience so far as been they assume a REST API on the backend and otherwise want to be in charge of the DOM inside them. Robert Roskam On Monday, February 5, 2018 at 5:26:25 PM UTC-5, Tom Forbes wrote: > > > Perhaps we should just be able to swap Forms with WTForms or another > python library and bake in ElementUI, > > There are a plethora of UI frameworks with different tradeoffs, I really > don't think Django sound pick one. > > However a stronger integration with the JS-build tools of the day like > Yarn, webpack et al would be a good step in the right direction, and more > agnostic than just 'use this UI framework we picked for you'. > > > perhaps it's time for npm to become a first class citizen. > > I think if Django is going to stay relevant to building most/all kinds of > web apps this is something that will need to happen. To be fair, npm and > the whole frontend ecosystem has only really 'matured' in the last couple > of years, it's come a long way since Django started. > > On 4 Feb 2018 00:36, "Jamesie Pic" <[email protected] <javascript:>> > wrote: > > On Thu, Feb 1, 2018 at 12:46 PM, Marc Tamlyn <[email protected] > <javascript:>> 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 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] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > 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/2213a3ba-a4e3-4e3c-b022-f81c01ce3c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
