Can we please have some discussion over adding "required" and "error"
HTML classes to fields in newforms as_ methods?
Two tickets of relevance:
http://code.djangoproject.com/ticket/3512
http://code.djangoproject.com/ticket/3515
It'd be good to see a design decision for this (and if 3512 is good,
On Apr 3, 4:48 am, "Waylan Limberg" <[EMAIL PROTECTED]> wrote:
> If I recall correstly that was a design decision as you can always nest
> with tags:
I'm not sure if this was an official design decision. As the ticket
writer, I suggested that this was a solution.
The tag could easily be extended
On 4/2/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> On 4/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > Anyone have strong opinions against this before I whip up a patch?
>
> +1 on adding "headers", -1 on adding (for the same reason we
> leave out).
-1 on for the same reason.
As for
James Bennett wrote:
> Another possible improvement would be -- since we're outputting XHTML
> here -- to also include the wrapping around the
> output, since the 'tbody' element is not implied in XHTML (though
> we're not providing the wrapping , or the wrapping
> in as_list(), which seems weir
Hi guys!
I've done a patch to the "with" tag be able to accept multiple
assignments without the need to nest many with tags, look the
following example:
{% with complicated.var.name1 as name1 and complicated.var.name2 as
name2 %}
{{ name1 }}, {{ name2 }}
{% endwith %}
I reopened the proper tag:
On Mon, 02 Apr 2007 10:53:39 -0400, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Hi guys!
>
> I want to be able to use with as:
>
> {% with some.complex.variable as var and some.another.variable as
> other %}
> {{ var }}
> {{ other }}
> {% endwith %}
>
> I saw some discussion about this som
On Apr 2, 2:50 am, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> On 4/1/07, SmileyChris <[EMAIL PROTECTED]> wrote:
>
> > I'm not sure if there's a ticket for this, but I remember talk about
> > it being an unnecessary wart which was going to be removed eventually.
> > Is it in the 1.0 plan?
>
> Y
Hi guys!
I want to be able to use with as:
{% with some.complex.variable as var and some.another.variable as
other %}
{{ var }}
{{ other }}
{% endwith %}
I saw some discussion about this sometime ago but I could not find the
thread. Now it is not possible to use the "and" as I want, is this a
d
On 4/2/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 4/2/07, Wolfram Kriesing <[EMAIL PROTECTED]> wrote:
> > 1) How can I help getting this functionality into trunk? (enhance the
> > patch, write doc, ...)
> > 2) Is this something that would be accepted to go into the trunk at all?
>
> W
On 4/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
> Anyone have strong opinions against this before I whip up a patch?
+1 on adding "headers", -1 on adding (for the same reason we
leave out).
Jacob
--~--~-~--~~~---~--~~
You received this message because you a
On 4/2/07, Wolfram Kriesing <[EMAIL PROTECTED]> wrote:
> 1) How can I help getting this functionality into trunk? (enhance the
> patch, write doc, ...)
> 2) Is this something that would be accepted to go into the trunk at all?
When I worked on this, the "fields" bits from the patch didn't seem to
There is an existing ticket
(http://code.djangoproject.com/ticket/3275), which had been partially
implemented (http://code.djangoproject.com/ticket/3275#comment:10).
This commit adds the depth parameter, nice thing. Thanks!
The second parameter "fields" has not been added yet. It can help
reduce
Localflavour need not to handle the field replacing. I'm proposing
only to create the base that allow it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email
On Mon, 2007-04-02 at 02:50 -0700, ElGranAzul wrote:
> Hi all.
>
> I'm working in the Spanish localflavour (to be released today or
> tomorrow), and I want to propose a standard way to define locale
> validations. It could help to developers to create the content and,
> for example, using introsp
Hi all.
I'm working in the Spanish localflavour (to be released today or
tomorrow), and I want to propose a standard way to define locale
validations. It could help to developers to create the content and,
for example, using introspection select the correct locale. It only
could be done if there
> I think we might have discussed this before, but the discussion
> fizzled out. What would you want to style -- the form HTML tag itself?
> The ? The table row (in case of as_table())?
>
> Adrian
i'd like to see the data type classes from oldforms re-applied to the
form elements in new forms. e.
16 matches
Mail list logo
