Re: Very bad experience in Django...

Joshua Partogi wrote: > > You need to define required=False > > On Thu, Jun 25, 2009 at 10:24 PM, steveneo > wrote: if steveneo got `Very Bad experience`, maybe i got `Very..very... n very... bad experience`, but i still learning django ^_^ *There`s no magic, its

Re: Very bad experience in Django...

Chris Withers wrote: > steveneo wrote: >> I try to use Django in a new project. Honestly, it is very bad >> experience. It looks not boosting my development speed. Today, I >> almost give up and begin to look up another Python framework > > Go for it :-) +1 /L --~--~-~--~~--

Re: Very bad experience in Django...

> you'll see it doesn't say anything about the validation behavior being > dependent on the widget in use.  So it doesn't matter what widget you use, > if you want to be able to validate False as a valid value, then you need to > include required=False in the form field definition. To be complet

Re: Very bad experience in Django...

On Thu, Jun 25, 2009 at 9:46 AM, Chris Withers wrote: > > steveneo wrote: > > BooleanField limits only to CheckBox? But I set > > widget=HiddenField It does not report error. HTML renders > > correctly, but actually, you can not use like that?! > > Didn't you hear me: I said go find another f

Re: Very bad experience in Django...

Chris, I don't know you. But I hope your day gets a little better and your problems lighter. Sincerely, Richard On 6/25/09, Chris Withers wrote: > > > steveneo wrote: > > BooleanField limits only to CheckBox? But I set > > widget=HiddenField It does not report error. HTML renders > > corr

Re: Very bad experience in Django...

On Thu, 2009-06-25 at 06:43 -0700, steveneo wrote: > BooleanField limits only to CheckBox? But I set > widget=HiddenField It does not report error. HTML renders > correctly, but actually, you can not use like that?! http://docs.djangoproject.com/en/dev/ref/forms/fields/#booleanfield You sho

Re: Very bad experience in Django...

steveneo wrote: > BooleanField limits only to CheckBox? But I set > widget=HiddenField It does not report error. HTML renders > correctly, but actually, you can not use like that?! Didn't you hear me: I said go find another framework, Django obviously sucks because one new user can't get hi

Re: Very bad experience in Django...

BooleanField limits only to CheckBox? But I set widget=HiddenField It does not report error. HTML renders correctly, but actually, you can not use like that?! On Jun 25, 11:22 pm, Chris Withers wrote: > steveneo wrote: > > I try to use Django in a new project. Honestly, it is very bad >

Re: Very bad experience in Django...

steveneo wrote: > I try to use Django in a new project. Honestly, it is very bad > experience. It looks not boosting my development speed. Today, I > almost give up and begin to look up another Python framework Go for it :-) Chris -- Simplistix - Content Management, Zope & Python Consultin

Re: Very bad experience in Django...

On Jun 25, 1:24 pm, steveneo wrote: > I try to use Django in a new project. Honestly, it is very bad > experience. It looks not boosting my development speed. Today, I > almost give up and begin to look up another Python framework > > One question,  does anyone use a hiddenInput in Form?  Som

Re: Very bad experience in Django...

You need to define required=False On Thu, Jun 25, 2009 at 10:24 PM, steveneo wrote: > > I try to use Django in a new project. Honestly, it is very bad > experience. It looks not boosting my development speed. Today, I > almost give up and begin to look up another Python framework > > One que

Very bad experience in Django...

I try to use Django in a new project. Honestly, it is very bad experience. It looks not boosting my development speed. Today, I almost give up and begin to look up another Python framework One question, does anyone use a hiddenInput in Form? Something like: class ProfileForm(forms.Form):