Check out djangobook.com. It's a much longer tutorial, and really well written.
On Jul 8, 4:07 pm, Bradley Hintze <bradle...@aggiemail.usu.edu> wrote: > Thanks, that helps but I wish Django had more tutorial than one. I > seem to learn by example. I am trying to make an form for uploading > files but no matter how many times I read the documentation I cant > seem to get the form to the client, let alone how to store the file. > Do you know how to get objects from your model (FileForm) to your > template? > > On Thu, Jul 8, 2010 at 5:51 PM, CLIFFORD ILKAY > > > > > > <clifford_il...@dinamis.com> wrote: > > On 07/08/2010 05:23 PM, Bradley Hintze wrote: > > >> I guess I just don't like the model.py, views.py, templates, and > >> url.py. In the tutorial you have to edit all of these and THEN you get > >> something that you can send to the client. It's very confusing! How do > >> they tie together? I probably need to do the tutorial again. It seems > >> to me getting info from the user should be strait foreword but its not > >> as displayed by the rather lengthy tutorial. But than I'm new to > >> this... > > > It's actually pretty simple and logical. Here is a possibly over-simplified > > overview. > > > models.py is where you model your problem. If you have an entity "Books", > > you would have a Book model along with its attributes. From this model, > > Django will generate the database objects once you run syncdb. > > > urls.py is the place where you specify what happens when a particular URL is > > requested. Django goes down the list of your regular expressions in there > > until it finds a match (or doesn't). Once it finds a match, the request is > > passed to the view function for that match. If it doesn't find a match, > > Django raises a 404 exception. > > > views.py is where you have the various functions that are invoked from > > urls.py handle the requests and pass the results to templates. > > > The templates are just HTML files with special tags embedded in them. Think > > of the tags as "holes" on the page that will eventually get filled by the > > data coming from view functions. > > > The Django framework ties all this together. For the purpose of the tutorial > > and for writing apps, you really don't need to know the details of how it > > does that but of course if you want to, you can. > > -- > > Regards, > > > Clifford Ilkay > > Dinamis > > 1419-3266 Yonge St. > > Toronto, ON > > Canada M4N 3P6 > > > <http://dinamis.com> > > +1 416-410-3326 > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django users" group. > > To post to this group, send email to django-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/django-users?hl=en. > > -- > Bradley J. Hintze > Graduate Student > Duke University > School of Medicine > 801-712-8799 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
