The problem with bootstrapping code like this is that it's great for a super simple project, but you instantly want to customise it for any project of any serious scope.
It seems to me a perfect candidate for a simple external project, although you may wish to have a different API so it's more reusable and extensible. In the event that a code part of this (a serialising component similar to a ModelForm for example?) which was usable in different ways then this might be a suitable candidate for inclusion. It's worth noting for example that there are multiple libraries which take model forms and render them completely differently - floppy forms and crispy forms being the best known. The primary purpose of ModelForm is to be a form, the rendering is a basic example to build from. Django rest framework serialisers I believe have some way of rendering a subset of model fields like this, that may be of some interest to you. Marc On 13 August 2015 at 05:00, Bernd Wechner <bernd.wech...@gmail.com> wrote: > I asked this question on the user group and got no reply fast, so I just > wrote a derived class to do it quickly: > > https://groups.google.com/d/msg/django-users/n87bFh8IYYc/MhkNmVBDAwAJ > > it's a hack and not what I'd call a patch, but one user liked it and asked > that I seek it's inclusion in Django. > > The justification is on that user page already, but in summary is to drive > for some presentation consistency between ModelForm and DetailView to > enable simple consistent rendering of generic forms or views in the same > manner. > > I'm new to Django, wouldn't say I'm a django developer (excepting I'm > trying to build a simple website with it and learning it and doing a proof > of concept at home ;-) so I'm certainly not up for contributing code per > se, but think this serves as a demo for a simple patch that I think Django > would benefit from. > > Regards, > > Bernd. > > -- > 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 django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/a0e2e4ad-160e-4472-96c5-370e58a0ed9d%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/a0e2e4ad-160e-4472-96c5-370e58a0ed9d%40googlegroups.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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1Go8bJZQyvpVJ9B_Np91tan-juurgtWAhXhcfEfZr04UA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
