On Wed, Dec 15, 2010 at 02:50, cocolombo <cocolo...@gmail.com> wrote: > Thanks so much Mike, Christophe, Venkatraman, and whoever joins in, > for your answers. > > To Venkatraman S: > > Yes quite a lot of the applications is written an are functioning > independently. > > As I described it's the "big picture" I have difficulty with, not > coding the individual parts that I need.
I would reiterate the need to build something - when starting, I also found myself in your situation - lots of documentation, no idea how to fit it all together. I did the tutorials twicve trying to learn, but failing to follow it up with action. When I actually sat down to make a site, a year or so later, it started to fall into place bit by bit. I've had troubles, but IRC and this mailing list have been a great help. I've had to re-write my very simple site twice, but I'm glad I did it wrong the first two times. I'm still not much of a Django head, but bit by bit I'm getting there. Start your project. Work it out as you go. Big hints: - use South from day one. It's hard to grok initially, but makes re-writes a little easier. - keep your code in version control. cheers L. > > Thanks again. > > cocolombo > === > > On Dec 14, 7:44 am, Mike Seidle <m...@seidle.net> wrote: >> Cocolombo - >> >> Actually, you are asking some pretty good questions because all of them are >> fundamental, and everyone starting with Django has to answer them. >> >> On Monday, December 13, 2010 10:25:45 pm cocolombo wrote: >> >> > I read a lot of documentation and books but there are still some very >> > basic things that I just don't catch about Django. >> >> > Let's say I want to crate a very basic site for a simple game with no >> > graphics, just text. >> >> > 1) Should the players use the admin to loggin ? >> >> Probably not. Most of the time I use Django-admin to administer an >> application, and that freesme from having to spend lots of time building out >> the back end of my app that will be used by a tiny number of people. This in >> turn frees me to develope the front end of my app that will be used by >> thousands. >> >> > 2) Do I use the user objects, to keep information about each players ? >> > Or a different class called player ? >> >> It depends on what you want to do. Django's user model lets you specifiy one >> model as a user profile, and so in your case it may make sense for the >> profile >> model to be called player. >> >> > 3) Should I create a separate application for the login section of the >> > site ? >> >> You may or may not have to create a seperate application. >> >> >> >> > 4) Is registering a new user (confirmation by email, etc) a different >> > module or is it part in the admin. >> >> You'll have to do a little assembly. See "Other Built in Views" here: >> http://docs.djangoproject.com/en/dev/topics/auth >> >> > 5) I understand the importance of admin to manage my database, but of >> > course, I don't want the players to access directly the database. Do >> > the players access the admin with limited privileges, or do they not >> > touch the admin whatsoever ? >> >> I don't think in your case you want users using the admin. >> >> > As I said I read a lot, but I am stucked and don't understand the "big >> > picture" of an application (or is it a project) ans it's relation with >> > the admin. >> >> Look at the admin as the control panel for your game's administrators. It >> can >> be used to access and modify pretty much everthing. >> >> > Thanks for taking the time to answer such questions that must be so >> > trivial to many of you. >> >> Two immutable truths: a broken clock is accurate two times per day, and >> everyone was new once. > > -- > 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. > > -- "... imagine a puddle waking up one morning and thinking, 'This is an interesting world I find myself in - an interesting hole I find myself in - fits me rather neatly, doesn't it? In fact it fits me staggeringly well, must have been made to have me in it!' This is such a powerful idea that as the sun rises in the sky and the air heats up and as, gradually, the puddle gets smaller and smaller, it's still frantically hanging on to the notion that everything's going to be alright, because this world was meant to have him in it, was built to have him in it; so the moment he disappears catches him rather by surprise." Douglas Adams -- 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.
