Re: newforms: proposal ModelForm Baseclass for model related Forms

2007-02-12 Thread RonnyPfannschmidt
every time someone wants to edit something On 12 Feb., 17:43, "Honza Král" <[EMAIL PROTECTED]> wrote: > On 2/12/07, Scott Paul Robertson <[EMAIL PROTECTED]> wrote: > > > > > On Mon, Feb 12, 2007 at 07:45:52AM -0800, RonnyPfannschmidt wrote: > > &

Re: Adding support for replacing the auth User model to fit custom needs

2007-02-12 Thread RonnyPfannschmidt
sweet - thats a good start On 12 Feb., 17:21, "Gary Wilson" <[EMAIL PROTECTED]> wrote: > On Feb 12, 9:01 am, "RonnyPfannschmidt" <[EMAIL PROTECTED]> > wrote: > > > in some case the only way to do it right is a replacement (like using > > a m

newforms: proposal ModelForm Baseclass for model related Forms

2007-02-12 Thread RonnyPfannschmidt
The actual method of creating Model related forms is a set of functions returning form classes thats nice to use, but not very nice to extend Im proposing a Base class wich allows to pass models/instances to generate forms, or inherit to extend the forms default usage would be ModelForm(model=

Re: Adding support for replacing the auth User model to fit custom needs

2007-02-12 Thread RonnyPfannschmidt
adding a profile doesnt fix all problems in some case the only way to do it right is a replacement (like using a mail as username) some might argue you could use profiles to do this stuff, but that would encourage messy code, denormalized data models and not really good practices to make it work

Adding support for replacing the auth User model to fit custom needs

2007-02-12 Thread RonnyPfannschmidt
The build-in User model is nice in many Cases, but sometimes it just is a bad limit for Development cause of its limits, but just droping it would cause the loss of all auth features, and doesnt play well with 3rd Party apps Examples are : * Email as Username * _long_ Usernames * special Characte

Adding support for replacing the auth User model to fit custom needs

2007-02-12 Thread RonnyPfannschmidt
The build-in User model is nice in many Cases, but sometimes it just is a bad limit for Development cause of its limits, but just droping it would cause the loss of all auth features, and doesnt play well with 3rd Party apps Examples are : * Email as Username * _long_ Usernames * special Characte

Adding Support for optional relations to Unregistred Users in the Database

2007-02-12 Thread RonnyPfannschmidt
Right now there is no Support for relating Data like Permissions, Posts, Comments, Wikipages and others to Unregistred Users The usual Solutions are nullable Relations, but * they break select_related An selfmade special User, but * checking if its the anonymous User is Complicated My Proposal

Re: newforms feedback

2006-12-26 Thread RonnyPfannschmidt
Hi, i just took a look at newforms, and the Lack of Function/Method based Validators makes my work harder. I'd like to see an Interface where i could define any Number of Form-methods beginning with "clean_fieldname_" to define multiple custom Validators for some Fields, as well as more than one