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. Thanks again. cocolombo === On Dec 14, 7:44 am, Mike Seidle <[email protected]> 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
