Re: Community page update

Hello, Thanks for the report. This problem has happened intermittently in the last few days. You can follow its resolution here: https://code.djangoproject.com/ticket/16339 Best regards, -- Aymeric Augustin. On 24 juin 2011, at 16:30, Thierry wrote: > The update for the community page doesn

Reversing translated urls in templates

Hi, I would like to get some feedback on https://code.djangoproject.com/ticket/16332 Jacob suggested that the standard url-tag should take a lang argument so we don't need an extra tag (okay, his actual concern was the dislike of the name i18n_url ;)). I would like that idea too, but I am somewhat

Reversing translated urls in templates

Hi, I would like to get some feedback on https://code.djangoproject.com/ticket/16332 Jacob suggested that the standard url-tag should take a lang argument so we don't need an extra tag (okay, his actual concern was the dislike of the name i18n_url ;)). I would like that idea too, but I am somewhat

Re: Form Rendering API Proposal

I just want to quickly add a second mention for the importance of being able to control row-level groupings of fields, as well as row-level attributes such as classes. It's a problem I've run into many times and would love to have included in the new form-rendering solution. All the best,

Conditional aggregations.

This topic is discussed on the Ticket #11305 : https://code.djangoproject.com/ticket/11305 Like many folks, I am hit by the scenario where a relative simple query become a design decision because my «boss» asked me : "Hey Stan, can you add me a column with the number of valid items in each catego

Community page update

The update for the community page doesnt seem to be working https://www.djangoproject.com/community/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe fro

Re: max_value bug (ticket #16306)

On Wed, Jun 22, 2011 at 10:56 AM, Shawn Milochik wrote: > https://code.djangoproject.**com/ticket/16306 > > Would a core dev or two please give their opinion on this? I think it's > a bug and not a flaw in the documentation. As I read the docs it seems

Re: Form Rendering API Proposal

Hi Jacob, 2011/6/23 Jacob Kaplan-Moss : > Hi Idan et al. -- > > Thanks for putting this all together! > > In general, I like this a lot, and I'm always going to defer to the > eyes of someone like Idan who spends more time wrangling templates > than I do. So I like the general gist, and I most don

Re: Form Rendering API Proposal

Hi Preston, 2011/6/23 Preston Timmons : > This looks excellent so far. > > Do {% formfield %} and {% formrow %} accept context like {% form %} > does? > > Is there a way with {% formfield %} or {% formrow %} to set custom > attributes like placeholder, autocorrect, etc.? I find this common > requi

Re: Form Rendering API Proposal

Hi Jonas, 2011/6/23 Jonas H. : > On 06/23/2011 02:11 PM, Harro wrote: >> >> - Will the as_* methods on forms be deprecated? They seem to be a nice >> shorter version then the new way to do it. > > I'd rather provide a shorter version of {% form %} for built-in layouts: > > {% form foobar 'table' %

Re: Form Rendering API Proposal

Hi Benoît, 2011/6/24 Benoît Bryon : > > Le 23/06/2011 13:25, Idan Gazit a écrit : >> >> >> http://www.scribd.com/doc/57270484/Djangocon-EU-2011-Revised-Form-Rendering-Lightning-Talk-by-Gregor-Mullegger >> > > I'm still not convinced by the {% form myform hidden "honeypot" %} syntax. I have also n

Re: Form Rendering API Proposal

Le 23/06/2011 13:25, Idan Gazit a écrit : http://www.scribd.com/doc/57270484/Djangocon-EU-2011-Revised-Form-Rendering-Lightning-Talk-by-Gregor-Mullegger I'm still not convinced by the {% form myform hidden "honeypot" %} syntax. Isn't it a duplicate of {% widget HiddenInput for form.honeypot %

Re: Form Rendering API Proposal

Le 24/06/2011 01:02, Carl Meyer a écrit : On 06/23/2011 04:43 PM, Jacob Kaplan-Moss wrote: The wrong performance benchmarks could result in a veto from me; this is important. I really think templated form-rendering is a massive improvement in Django for front-end devs, so I'm very hopeful that

Re: Form Rendering API Proposal

Le 24/06/2011 06:42, Jjdelc a écrit : {% formconfig widget "forms/widgets/textarea.html" for "comment" %} or even {% formconfig widget "comment" using "forms/widgets/textarea.html" %} in order to mantain the same syntax for {% formconfig %}. +1 A consistent syntax for all form components woul