+1. (+10 if I can)
This kind of customization will help community to integrate many
css/js/html frameworks into Django with custom apps.
Felipe 'chronos' Prenholato.
Linux User nº 405489
Home page: http://devwithpassion.com | http://chronosbox.org/blog
GitHub: http://github.com/chronossc/ | Twitt
+1
This would be great.
On Thursday, March 7, 2013 12:42:29 PM UTC-7, Bruno Renié wrote:
>
> Hello,
>
> There was some discussion on the current limitations of the ModelForm
> API in the past couple of days on IRC, I'd like to make a proposal to
> address some of them.
>
> I wrote django-flop
Hi Bruno,
On 03/07/2013 12:42 PM, Bruno Renié wrote:
> * Move formfield_for_* to ModelForm and document them as public APIs
> * Deprecate `formfield_callback`
> * Write an AdminModelForm class that implements all the admin form
> fields and widgets customization
> * Modify ModelAdmin to make use o
Other possible option is for ideas:
http://django-crispy-forms.readthedocs.org/en/latest/index.html
;)
2013/3/7 Loic Bistuer
> +1
>
> This logic would be better in `ModelForm`.
>
> --
> Loic
>
> On Mar 8, 2013, at 2:42 AM, Bruno Renié wrote:
>
> My proposal is to move that field customization
+1
This logic would be better in `ModelForm`.
--
Loic
On Mar 8, 2013, at 2:42 AM, Bruno Renié wrote:
> My proposal is to move that field customization API from the
> ModelAdmin class back to ModelForm:
--
You received this message because you are subscribed to the Google Groups
"Django dev
Hello,
There was some discussion on the current limitations of the ModelForm
API in the past couple of days on IRC, I'd like to make a proposal to
address some of them.
I wrote django-floppyforms, a library that lets you render forms using
templates instead of python code. It behaves exactly like
