> I think you need to work on your workflow a little more. You will > definitely need to play with views; I'm not sure what you think > signals will acheive. > > You need to think in terms of "what HTML pages can I present to the > user, in what order; and what conditions must be met to move from page > 1 to page 2". > > The other red flag that is waving to me is the 'baseball_approved' > attribute. From the description of your workflow, it isn't obvious > that you actually want to/need to store unapproved objects in the > database. If you don't need to, drop that flag, and just refrain from > saving the model until you have an 'approvable' set of data.
Alright, let me explain it a little better without being so catious about the nature of the app. This app will be storing scores from the Wii game Wii Sports. So I essentially had thought that all 5 sports would be on one page and people could input their scores and upload a screenshot. Now, the reason the approved attribute is there is so if a person's score is reported as fake (e.g., no screenshot or fake screenshot), then I could it in the admin and the score would then be taken out off the rankings page and marked to the user accordingly. So it isn't so much a step 1, step 2, so much as each sport will have it's own line with two fields, score and screenshot upload. This is really the only way I could think of doing it (not being a programmer by trade mind you). Thanks for the help so far though Russ. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
