Hallöchen! My first Django project was a single application. Probably most of you started this way, with only some other applications shipped with Django installed on the same site, too.
However, I now prepare my second Django application which will be used together with the first one. For me, this is no problem. But I wonder how to write an application which can be easily integrated by others into their eco system. For example, get_profile() can only be connected with one model per site. But every application may have its own UserDetails, so get_profile must actually be considered harmful, unless you know for sure that your application will never be used somewhere else. http://code.djangoproject.com/ticket/3011 has the same problem, namely that only one application can extend the global datastructures. I think that patching an application so that it doesn't login handling anymore (because another app does already) is okay, but for example substituting all get_profile calls is actually unnecessary. What do you think? Tschö, Torsten. -- Torsten Bronger, aquisgrana, europa vetus Jabber ID: torsten.bron...@jabber.rwth-aachen.de or http://bronger-jmp.appspot.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
