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
On Feb 25, 7:24 pm, Nick Craig-Wood wrote:
Sounds like your table and/or innodb/mysql install is broken. It's
hanging on updating statistics. Try REPAIR TABLE or google for
something like "mysql state statistics".
--~--~-~--~~~---~--~~
You received this message be
> Closures; fantastic. The more I learn about Python the shorter and
> shorter my code gets. :-)
Nathan, perhaps you can post a short excerpt of your code?
Closures are lovely and all, but newforms needs a few minor but
important design changes so it doesn't require us to do anything even
slight
> The solution is that clean_* methods should just be passed the field's
> value as an argument.
> Even being backwards incompatible, I think it needs to be done.
Absolutely, +1 here too. What was the argument against this?
--~--~-~--~~~---~--~~
You received this
> It is simple, Pythonic and doesn't change core :-)
Pythonic sure, but not even close to what I would consider simple.
Surely we can find better, simpler, cleaner solutions to these common
problems. I'll gather some code so we can all see what a mess these
few trivial omissions are making.
--~
> class MyForm(Form)
>field1 = ...
>field2 = ...
>
>def generic_clean(self):
> # ...
>
>clean_field1 = generic_clean
>clean_field2 = generic_clean
The problem here is generic_clean doesn't know which field it is, an
> I've accomplished the same thing with a template filter called "bunch"
> -- it converts a list into a list of tuples that have been bunched.
> I'd rather add a "bunch" filter than make this change to the regroup
> tag, because this would completely change the meaning of the regroup
> tag.
Sound
Another one --
6. Maybe allow clean_method=x in field parameters, rather than have to
create a custom field or repeat similar clean functions.
> 5. (Somewhat pedantic) Rename data[] to raw_data[] and cleaned_data[]
> to data[] - Has anyone seen how unnecessarily ugly this can get?
Sorry I take
Hello all, I have some suggestions for newforms, which I've condensed
into point form, excuse me if they seem a little blunt they are just
meant to be concise --
1. Magic cleaned_data - So we can get/set values out of order and
before the clean() run, having themselves clean implicitly as
requir
Hi all I have a patch to the regroup tag which allows --
Regroup into any number of groups, of set size --
{% regroup list every 4 as grouped %}
Regroup into set number of groups, at any size --
{% regroup list into 4 as grouped %}
I've found this indispensable in rendering unordered lists wher
Been hacking admin a bit lately and wondering if anyone else thinks
the following couple of minor improvements would help.
1. An extra_context on the admin view functions? Allowing you to
easily hack not only the template for a particular admin page, but
also the view!
2. The template selection
> Unclear opinion
> - [EMAIL PROTECTED]
I'm a definite +1 on this, whether it's {{ MEDIA_URL }} or {%
MEDIA_URL %} I don't mind.
Lets not forget though, it's a VERY common case to have more than just
MEDIA_URL being needed from settings.py. Obviously not all of it
though. I seem to recall Smiley
Perhaps even a single page, that lists all backwards-incompatible
changes, by their version of introduction to trunk? I've already used
newforms in production, so stuff like this is kinda important.
--~--~-~--~~~---~--~~
You received this message because you are s
Yes it really does need to be there! Out of the box.
It's omission contradicts the whole concept of serving media
separately; not to mention being an unnecessary 'what the ?' hurdle
for newcomers.
--~--~-~--~~~---~--~~
You received this message because you are su
Sorry Jacob, new post here --
http://groups.google.com/group/django-users/t/2bcc79251b693a05
On Apr 13, 12:59 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> On 4/12/07, sime <[EMAIL PROTECTED]> wrote:
>
> > I'm looking for a talented local program
I'm looking for a talented local programmer to help with a growing
workload, on a regular contract basis. All projects in django :-)
Or if you have experience working remotely that could work too.
--~--~-~--~~~---~--~~
You received this message because you are su
On Feb 20, 11:30 am, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> But I suppose that you are talking about using MEDIA_URL to access CSS
> and JS files, right? If yes then it's not what everyone does. Many
> people keep CSS and JS under source control in a place that has nothing
> to do with a direc
Hi all - interested to hear feedback on a minor but I feel important
addition to allow MEDIA_URL and other selected constants to be
accessible from templates --
http://code.djangoproject.com/ticket/1278#comment:6
Particularly important for new users (like me a couple days back). I
was scratching
Yeah I like the ModelForm class idea better, for sure. Are you coding
it or will I?
On Feb 13, 3:13 am, "RonnyPfannschmidt" <[EMAIL PROTECTED]>
wrote:
> that wouldnt remove the strict distinction betwen form_for_model
> and form_for_instance (the only difference i see, is that one of them
> has
OK here's my new patch, adds a css='bla' option to your field
definitions, also class='bla error' when there's an error, and
class='bla required' when the field is required (thanks waylan for the
idea on those last two points) --
http://code.djangoproject.com/ticket/3515
On Feb 16, 10:12 am, "Bri
Hey Wayne - I just submitted something similar - check it out
http://code.djangoproject.com/ticket/3515
On Feb 17, 6:57 am, "waylan" <[EMAIL PROTECTED]> wrote:
> FYI: I opened a ticket (#3512) and uploaded three separate patches.
> Personally, after working out all three, I think I prefer the thi
On Feb 16, 10:12 am, "Brian Morton" <[EMAIL PROTECTED]> wrote:
> I don't know if this has been suggested yet, but has anyone considered an
> enhancement to newforms to optionally allow a field to have a different
> class if it has an error? It would be helpful for things like making error
> field
22 matches
Mail list logo
