Newforms and generic views

Hi folks,

Can anyone share information regarding the current timeline
and plans 
for newforms and integrating newforms with generic views? I
did look 
over the website and searched the archives of the dev group
but didn't 
see a recent estimate. I'd gladly help out, but I'm somewhat
new to 
Django and it seems there are already quite a few chefs in
the 
kitchen. ;)

What led me down this path--besides general interest and
planning 
concerns--is an investigation into how best to present
errors using 
generic views in a list format. It appears that newforms
includes an 
"errors" property, while oldforms errors can be
accessed using 
"error_dict." At the same time, I'd like to
highlight fields with 
errors using a custom style, but don't see how to pass a
style to form 
fields when used with generic views. [Does that make sense?
Basically 
I'd like to show an error list and mark fields with a red
border when 
there are errors, instead of listing error messages next to
each 
individual form element.]


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On 1/29/07 3:28 PM, Mike wrote:
> Can anyone share information regarding the current
timeline and plans 
> for newforms and integrating newforms with generic
views? 

Generally we don't really put out "timelines"
per-se.

You see, we're all volunteers around here, and committing to
a solid timeline 
seems the best way to ensure that we miss it.  Until we've
got people who 
actually get paid full-time to work on Django[*], this is
how it'll be.

> I did look 
> over the website and searched the archives of the dev
group but didn't 
> see a recent estimate. I'd gladly help out, but I'm
somewhat new to 
> Django and it seems there are already quite a few chefs
in the 
> kitchen. ;)

Actually, though, there hasn't been anyone who's (so far)
volunteered to work 
on bring newforms into generic views. So, if that's
something you'd like to 
work on, we'd all love it if you jump on over to django-dev
and offer your 
services.

> What led me down this path--besides general interest
and planning 
> concerns--is an investigation into how best to present
errors using 
> generic views in a list format. It appears that
newforms includes an 
> "errors" property, while oldforms errors can
be accessed using 
> "error_dict." At the same time, I'd like to
highlight fields with 
> errors using a custom style, but don't see how to pass
a style to form 
> fields when used with generic views. [Does that make
sense? Basically 
> I'd like to show an error list and mark fields with a
red border when 
> there are errors, instead of listing error messages
next to each 
> individual form element.]

FYI, this is usually how I do it::

	<div class="form-row {% if form.errors%}error{%
endif %}">
		{{ form.field }}
	</div>

Then I can use a CSS rule like::

	div.error input { ... }

To stype fields with errors.

Sensemakemuch?

Jacob

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On 1/29/07 3:57 PM, Jacob Kaplan-Moss wrote:
> actually get paid full-time to work on Django[*], this
is how it'll be.

Dammit, I was gonna make a snarky joke about someone loaning
me a million 
dollars for a Django endowment, and then I went and clicked
"send" to early.

/me grumbles...

Jacob

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Jan 29, 4:57 pm, Jacob Kaplan-Moss <j...jacobian.org> wrote:
> On 1/29/07 3:28 PM, Mike wrote:
>
> > Can anyone share information regarding the current
timeline and plans
> > for newforms and integrating newforms with generic
views?Generally we don't really put out
"timelines" per-se.
>
> You see, we're all volunteers around here, and
committing to a solid timeline
> seems the best way to ensure that we miss it.  Until
we've got people who
> actually get paid full-time to work on Django[*], this
is how it'll be.
>
> > I did look
> > over the website and searched the archives of the
dev group but didn't
> > see a recent estimate. I'd gladly help out, but
I'm somewhat new to
> > Django and it seems there are already quite a few
chefs in the
> > kitchen. ;)Actually, though, there hasn't been
anyone who's (so far) volunteered to work
> on bring newforms into generic views. So, if that's
something you'd like to
> work on, we'd all love it if you jump on over to
django-dev and offer your
> services.
>
> > What led me down this path--besides general
interest and planning
> > concerns--is an investigation into how best to
present errors using
> > generic views in a list format. It appears that
newforms includes an
> > "errors" property, while oldforms errors
can be accessed using
> > "error_dict." At the same time, I'd like
to highlight fields with
> > errors using a custom style, but don't see how to
pass a style to form
> > fields when used with generic views. [Does that
make sense? Basically
> > I'd like to show an error list and mark fields
with a red border when
> > there are errors, instead of listing error
messages next to each
> > individual form element.]FYI, this is usually how
I do it::
>
>         <div class="form-row {% if
form.errors%}error{% endif %}">
>                 {{ form.field }}
>         </div>
>
> Then I can use a CSS rule like::
>
>         div.error input { ... }
>
> To stype fields with errors.
>
> Sensemakemuch?
>
> Jacob


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Hey Jacob,

Thanks for your pointer regarding error
highlighting--Igotsit.

> Actually, though, there hasn't been anyone who's (so
far) volunteered to work
> on bring newforms into generic views. So, if that's
something you'd like to
> work on, we'd all love it if you jump on over to
django-dev and offer your
> services.

I might just do that (you'll all be sorry ;).

In the meantime, let's ring in the year 1984 with our good
friend 
David Lee Roth:

http://youtube
.com/watch?v=fJPAG4V98vQ


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at htt
p://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---