On 12/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
The problem is visual. I do not like to present end users so ugly
looking errors. As temp. solution I have patched as_table() output, so
it takes optional argument:
errors_on_separate_row
So, now, when I call it from my application, I c
[EMAIL PROTECTED] wrote:
But in fact it does not look user intuitive.
I concur with this statement. I've got a form with about 10 fields and
when there are multiple errors for adjacent fields, it's very hard to
tell if the error is for the field above or below.
The problem is visual. I do n
Hi!
Today I tried to use django.newforms, and the first thing which I stuck
upon was the design of errors. Since we are using tables for our forms,
it seems to be hardcoded to use separate row to display errors. Not
sure how nicely to display errors - all I've achieved so far is that
varaint:
h
