On Dec 14, 3:04 pm, Shawn Milochik <shawn.m...@gmail.com> wrote: > Okay, here are a few ideas: > > 1. If you hate pop-ups, but aren't opposed to a little AJAX, then you could > do it that way. > > 2. You could do it with a multi-screen, 'wizard-like' set of templates. > > 3. You can keep state using session variables. > > 4. If you don't want to worry about keeping session variables, you can have a > menu somewhere listing the possible activities (add attendee, add venue, > etc.) If someone tries to do one, and finds that they don't have a required > item, they'll have to click a different menu item, do the creation, then > click the original choice and select the newly-added item. > > By the way, it doesn't sound right that you need an attendee for an event. > Events, in my imagination, always have zero or more attendees. Zero upon > creation, and possibly more as attendees register to attend. > > Of those items mentioned above, I prefer AJAX (using jQuery). However, > depending on the audience for your application, you may need to ensure that > it works on browsers that have JavaScript enabled, so you may choose another > route in addition to (or instead of) AJAX. > > I hope this was helpful. If not, let me know what I'm not understanding about > your questions. > > Shawn
Shawn, Thanks. I appreciate your time and assistance. You're right about Event/Attendee relationship, although there's a good reason for it when looking at my actual models and their purpose. And the fact that I lied, and Attendees are actually something else. One day I'll learn to give better examples of actual circumstances - just thought the analogy was good enough to get started, without other complicated context-sensitive information. The reason I'm opposed to pop-ups and multiple-separate-steps (your #4) is that I'm trying to streamline the process for the user, while taking a "progressive enhancement"/accessibility approach. I'd like to get the flow working "old-school", and then build in AJAX on top of that. In this case, a person creating an new Event would know all of the necessary details (Venue location, etc), but we may not have the Venue listed already, with the necessary meta-information. You've been a great help, and I suppose I'll push on until I hit another, more specific wall. Thanks again. -- 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.
