On 16/05/16 15:10, Carl Meyer wrote:
On 05/15/2016 11:01 PM, Curtis Maloney wrote:
So this seems to leave us only part way to removing rendering decisions
from the form code -- your widgets can be templated, but your form code
still needs to decide which widgets...
Yep, one step at a time. Wi
On 05/15/2016 11:01 PM, Curtis Maloney wrote:
> So this seems to leave us only part way to removing rendering decisions
> from the form code -- your widgets can be templated, but your form code
> still needs to decide which widgets...
Yep, one step at a time. With django-floppyforms templated widg
On 12/05/16 01:04, Preston Timmons wrote:
Hey Curtis,
I think you're asking how this patch will help with form and field layouts?
If so, not that much. It only addresses moving the widget HTML that
currently is hardcoded in Python into templates.
No... was all to do with widget rendering...
C
On 05/15/2016 09:58 PM, Carl Meyer wrote:
> Yuck. Is there only one admin widget that includes a built-in widget? If
> so, I think we would maybe be better off just duplicating that one
> built-in widget in the admin templates.
That should read "built-in template," not "built-in widget."
Carl
--
Hi Luke,
Could you clarify what you mean by "AJAX support in auth views"? Do you
mean the ability to submit requests to these endpoints and get JSON
responses back rather than HTML, so the process can be done more
client-side, or something else?
If you could link the patch too that would help roo
Hi all,
I've been using a patched version of Django for a while now that includes
AJAX support for the login/logout views in contrib/auth. I've searched the
django-developers mailing list and Trac tickets for any existing work on
this and haven't found anything. I'd like to make a PR, but am wo
