Re: RFC: Templatetag API for form rendering

2011-05-22 Thread Carl Meyer
On 05/22/2011 08:54 PM, Russell Keith-Magee wrote: > My argument: I'm trying to think of another example in Django's > template language where the template tag is an "action" in this way. > To my reading, outside of the tags used for logic (for, if, etc), and > tags that define a contextual block

Re: RFC: Templatetag API for form rendering

2011-05-22 Thread Russell Keith-Magee
On Mon, May 23, 2011 at 9:00 AM, Carl Meyer wrote: > > > On 05/22/2011 07:22 PM, Russell Keith-Magee wrote: >> On Mon, May 23, 2011 at 6:21 AM, Carl Meyer wrote: >>> Just had a quick conversation with Gregor and Chris Beaven on IRC; >>> based on a comment of

Re: RFC: Templatetag API for form rendering

2011-05-22 Thread Russell Keith-Magee
On Mon, May 23, 2011 at 8:44 AM, Carl Meyer wrote: > > > On 05/22/2011 07:18 PM, Russell Keith-Magee wrote: >> I like this. Simple, covers all the common use cases that I can see. >> My only feedback here would be mostly bikeshedding -- the fact that {% >> form %} is a

Re: RFC: Templatetag API for form rendering

2011-05-22 Thread Carl Meyer
On 05/22/2011 07:22 PM, Russell Keith-Magee wrote: > On Mon, May 23, 2011 at 6:21 AM, Carl Meyer wrote: >> Just had a quick conversation with Gregor and Chris Beaven on IRC; >> based on a comment of Chris', we discussed the possibility of ditching >> the {% formlayout %} tag

Re: Filtering on Many2Many Related Objects

2011-05-22 Thread Chris Beaven
Isn't the first suggestion (__contains) achievable already by just chaining two filters: Group.objects.filter(persons=p1).filter(persons=p2) ? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: RFC: Templatetag API for form rendering

2011-05-22 Thread Carl Meyer
On 05/22/2011 07:18 PM, Russell Keith-Magee wrote: > I like this. Simple, covers all the common use cases that I can see. > My only feedback here would be mostly bikeshedding -- the fact that {% > form %} is a configuration action, and {% renderform %} is the > rendering action. It feels to me

Re: RFC: Templatetag API for form rendering

2011-05-22 Thread Russell Keith-Magee
On Mon, May 23, 2011 at 6:21 AM, Carl Meyer wrote: > Just had a quick conversation with Gregor and Chris Beaven on IRC; > based on a comment of Chris', we discussed the possibility of ditching > the {% formlayout %} tag in favor of specifying the layout as an > argument to the

Re: RFC: Templatetag API for form rendering

2011-05-22 Thread Russell Keith-Magee
On Mon, May 23, 2011 at 4:21 AM, Gregor Müllegger wrote: > (You can read this RFC online if you prefer: > https://github.com/gregmuellegger/gsoc2011-stuff/blob/master/rfc_syntax.rst ) > > > Hi, > > like you might know I've prepared as pre-work to my GSoC project a repository

Re: RFC: Templatetag API for form rendering

2011-05-22 Thread Carl Meyer
Just had a quick conversation with Gregor and Chris Beaven on IRC; based on a comment of Chris', we discussed the possibility of ditching the {% formlayout %} tag in favor of specifying the layout as an argument to the {% form %} block tag. E.g. instead of >     {% form %} >         {% formlayout

[GSoC form-rendering] Weekly check-in -0.0

2011-05-22 Thread Gregor Müllegger
Hi, Carl and me had a vital discussion about the syntax that we will propose for a RFC. There is already a mailing list thread to which I warmly invite you to join: http://groups.google.com/group/django-developers/browse_thread/thread/e4836b5a9d36349e Read the templatetag syntax proposal there

RFC: Templatetag API for form rendering

2011-05-22 Thread Gregor Müllegger
(You can read this RFC online if you prefer: https://github.com/gregmuellegger/gsoc2011-stuff/blob/master/rfc_syntax.rst ) Hi, like you might know I've prepared as pre-work to my GSoC project a repository [1] with examples for two different approaches to my upcoming work on the form rendering.