On Jun 20, 12:13 pm, Andre Terra wrote:
> Have we moved forward with this issue at all? What is its current status?
I also maintain an external package that implements fieldsets (django-
form-utils [1]). Both django-form-utils and WTForm take the approach
of adding a Python data structure to Form
Have we moved forward with this issue at all? What is its current status?
Thank you in advance.
Sincerely,
André Terra
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/
Hello,
akaihola wrote:
>> Having just had a quick read fo the source -- this is the first time
>> I've heard of the project -- it looks well enough written. Akaihola does
>> know his stuff; we already know that. Possibly we wouldn't pull in the
>> whole project, but get a patch to add the fieldse
On 19 maalis, 02:24, Malcolm Tredinnick
wrote:
> Having just had a quick read fo the source -- this is the first time
> I've heard of the project -- it looks well enough written. Akaihola does
> know his stuff; we already know that. Possibly we wouldn't pull in the
> whole project, but get a patc
Definite +1. The lack of fieldsets has tripped me up plenty of times.
On Mar 19, 10:06 am, Jari Pennanen wrote:
> WTForm is simple implementation built on top of existing (new)forms to
> help create fieldsets, and by judging django snippets alone one can
> see it's a huge hole in Django. Everyon
If anyone else read this and was as confused as I was at first, make
sure to note that this is different than WTForms[1], which is an
alternate form library that took several of its cues from Django's
newforms.
[1] http://wtforms.simplecodes.com/
Thanks,
Eric Florenzano
--~--~-~--~~-
On Wed, 2009-03-18 at 17:06 -0700, Jari Pennanen wrote:
[...]
> I wish people has some thoughts about this...
Well, one thought is that your timing is a little off. We're in the
final phases of getting the 1.1-beta release out and then it's heads
down, fixing bugs for 1.1-final.
In a couple of m
I really hate to be a pessimist, but if the functionality already
exists for that much generation, why bother integrating it with the
main django package?
On Mar 18, 8:06 pm, Jari Pennanen wrote:
> WTForm is simple implementation built on top of existing (new)forms to
> help create fieldsets, an
WTForm is simple implementation built on top of existing (new)forms to
help create fieldsets, and by judging django snippets alone one can
see it's a huge hole in Django. Everyone has wondered why the heck
doing those fieldsets is such a pain when in admin it is super easy,
and it turns out the Dj
