#django

if you want to style fields on a form, whats the django way of doing that?

well, you can apply a class name to their widget's attrs

CSS?

or target the field by id

stackoverflow says "myfield = forms.CharField(widget=forms.TextInput(attrs={'class' : 'myfieldclass'}))"

well, yes, css...

personally, I feel putting presentation decisions in code is wrong...

but my IDE doesnt know what widget is

so what?

vendor_name = models.CharField(max_length=250, widget=forms.TextInput(attrs={'class':'input-large'}))

TypeError: __init__() got an unexpected keyword argument 'widget'

no

don't confuse Model fields with Form fields

oh shit

dont know why i didnt think of that!

hrmmmm...

i've got two formsets and i'm rendering them in their own form tags, as a result the view is complaining that the respective management form doesn't exist, thoughts ont he best way to deal with it?

i've thought about checking the post dict to see if the management form exists, but that seems like a bit of a hack

also considered using a try, but would prefer not to do that for good reasons

do i want to use crispyforms?

coderman1: floppy-forms or formulation or django-sniplayes.... from what I've seen of crispy forms, it still moves presentation into code

sniplates, even

(full disclosure: I wrote formulation and sniplates)

coderman1, i've used crispyforms, and it certainly does move presentation into code

FunkyBob, interesting, I'll have to look into those, why did you write formulation and sniplates?

cereal: I wrote the original sniplates a long time ago... from that I got the inspiration for formulatin

and then from that, in redesigning it, got the ideas for the new version of sniplates

it' all very inceptiony :P

ah i see

happens to pretty much everyone imo

I'll seriously have to look into formulation, crispy drives me nuts hah

but that's all i've ever heard heh

so i stuck with it

I'd recommend sniplates

that seems odd to me?

or did I read that in the wrong order?

ah, so you wrote sniplates, formulation then redid sniplates

missed that ;)

yep

I shall read the docs!

:)

FunkyBob, you might consider having a form example int eh docs? I'd imagine that's what most people will need right?

though I see how this is more than just simply a form tool

that's nice

Would like some clarification on formsets. There is formset_factory which is for forms that are not based on a model. There is modelformset_factory which like formset_factory generate many of the same kind of form but forms that are based on a model. Then there is inlineformset_factory which can tie two different forms that are connected by a foreign key.

Or rather, more specifically to the model formset aspect, the modelformset_factory and inlineformset_factory generate forms based on models.

You cant actually pass a prexisting form to those formsets

And in the case of the formset_factory you would have to pass an existing form to it in order to generate a formset

acmehandle, i'm reading what you said

i'm working with formsets right now actually so hopefully i can help

i'd imagine you might want to look into initial data?

acmehandle: I thought modelformset_factory was for creating formsets from a model

if i remember correctly that'll pre-populate your forms if that's what you are trying to get?

so it creates a formset of ModelForms

FunkyBob, yeah i think he said it that way

acmehandle, https://docs.djangoproject.com/en/1.7/topics/fo...

No, I think with modelformset_factory you have to pass the actual model, you dont pass the ModelForm to a modelformset_factory

correct, you pass the Model and it'll generate the ModelForm's from the model itself

you can specify the queryset however

Only with regular formset_factory do you pass a form

what are you trying to do?

Ok, wanted to be sure we were on the same page.

Not sure yet, I'm trying to figure out of modelformsets are what I need

you may be able to specify the form class, for the modelformset factory

well, what are you attempting to do?

Right, thats where I'm stuck at.

lol

i know that feeling all too well some days :(

some days, and some weeks.

I have a form and I want the user to be able to upload photos. So I dont know if I should allow the user to upload photos in the same form as say for example their user profile. Or redirect them to another page specifically for photos

doesn't look like the formset_factory will let you pass in a Form class, that seems silly

don't you mean modelformset_factory ?

but you can provide almost everything you'd hopefully need with a formset, for instance one of my formsets i'm passing in the fields and widgets override

FunkyBob, yes

if you already have a modelform, you don't need modelformset_factory

To clarify and correct what I was saying. modelformset_factory only accepts models

formset_factory only accepts forms

if you don't have a form, modelformset_factory will build the ModelForm _and_ Formset

where's the problem?

so...

I dont think you can customize the fields in a modelformset_factory

yes you can