I'm far from being an expert, but maybe you can look at the django-tagging code for inspiration:
http://code.google.com/p/django-tagging/ What they do is to provide a TagField in the tagging application, and then you can use that field in the form of the application using tags. You can probably do something similar with an AvatarField. - Paulo On Thu, Aug 6, 2009 at 4:07 PM, Andrin Riiet <c7r.s...@gmail.com> wrote: > > Hi, I'd like to shed some light on the "the right way" to make > applications in django by an example and a few questions. > > Let's say that I have a 'users' application (acting as "user profiles" > on the built-in user authentication system) and I want to add an > avatar image feature to it. > I'd like to have the avatars in a separate application in case my next > project doesn't require them (this is the right way to do things i > guess?) > > Now I want to have the user to be able to upload an avatar image in > the "edit profile" form. The default edit-profile form is defined in > my 'users' application of course. I'd like to "add" the avatar feature > (form field) to it somehow. - This is part 1 of the problem > > The 2nd part is in the form handling: the request object is going to > contain form field values from 2 different applications, none of which > should be responsible for processing the other's forms. > > Obviously the 'avatars' application is dependent on the 'users' > application but the 'users' application should be oblivious of the > avatars... > > How would I go about doing that? > > Andrin > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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 -~----------~----~----~----~------~----~------~--~---
