On Tue, Dec 14, 2010 at 8:55 AM, cocolombo <[email protected]> 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. > The docs and we are here to help :) But only if you spend sometime learning the bits yourselves. > > 1) Should the players use the admin to loggin ? > You can use the user-auth system in place. http://docs.djangoproject.com/en/dev/topics/auth/ > > 2) Do I use the user objects, to keep information about each players ? > Or a different class called player ? > You can use the Users object. If the player is different from that of a User, then you may create additional objects suitably - totally depends on how you have structured your game. > 3) Should I create a separate application for the login section of the > site ? > Check #1. > > 4) Is registering a new user (confirmation by email, etc) a different > module or is it part in the admin. > Refer django-registration > 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 ? > django-Admin doesnt manage your database - it provides an interface to look into what your schema contains. 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. > Did you try creating your app? Check out http://lightbird.net/dbe/ for more. -V http://blizzardzblogs.blogspot.com/ -- 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.
