DjangoBot: #django

like form processing, database access ..

not to be confused with templates

phpluv, we that view actually

ok what's called view is a controler

no

Not really.

no, it's a view ;)

phpluv, it's not as simple but from your point of view yeah

apart from being called view ... it has nothing of a view :)

we're not saying its a template, which is what equates to the view of mvc

phpluv: You're trying to see Django as an MVC framework, which it's not.

phpluv, it still decides what will be sent to the template for rendering

but a django view is /not/ a controller

can a view display data in different ways, ie. load different templates

sure

phpluv: it takes a request and returns a response - what happens in between is whatever you want to happen :)

right, i assumed it was one, i was wrong :)

if i do class X(forms.ModelForm): class Meta: model = m; x = X(data=data); x.is_valid() to trigger validation... then x.cleaned_data gives me an error... x has no attribute cleaned_data... is that wrong?

it's probably because it's from the publishing world

which is very interesting

__machine: did is_valid() actually pass/

is_valid failed...

then of course there's no cleaned_data

i'm actually getting the no attribute error in one of my clean_* methods which is trying to get it's data from cleaned_data and validate it

if a view can loead to different views of data, how can it be called A view ?

for the same field, or a different field?

lead*

phpluv: because its not the same view as in MVC

so stop reading more into the name

def clean_barcode): barcode = self.cleaned_data.get('barcode')

ok ok difficult :)

the 'view' of mvc is closer to the template

i like to cast tings in patterns :)

__machine: pastebin some full code, that should be fine unless something else is breaking things

that doesn't help if they don't actually fit

where can i see typical view code ?

etc