Re: Reusable/plugable apps integrations best practices

And what about doing the same way the Comment application (bundled with Django) works? I think that looking the way Comment app works could inspire you On Aug 24, 12:39 am, Richard Marko wrote: > Simple approach for this is to use try catch block to create proper > field like

Re: Reusable/plugable apps integrations best practices

Simple approach for this is to use try catch block to create proper field like this: from django.db import models try: from photos.models import Photo photo_field = models.ManyToManyField(Photo) except ImportError: photo_field = None class Standalone(models.Model):

Re: Reusable/plugable apps integrations best practices

You need to remove the references on one side or the other. You need to make a choice. will events manage photos, or will photos manage events, and so on. Then if events manage photos, you need to remove all references to events from the photos app. It sounds like it will take some reworking of

Re: Reusable/plugable apps integrations best practices

I'm intrested in the answer too On Aug 23, 1:36 am, "Chris H." wrote: > So I'm trying to get my head around making my small, tightly focused > apps reusable.  I've done this, but right now still have > "dependencies" between one another, that I'd like to remove.  For

Reusable/plugable apps integrations best practices

So I'm trying to get my head around making my small, tightly focused apps reusable. I've done this, but right now still have "dependencies" between one another, that I'd like to remove. For simplicity sake, I have an Articles, Events, and Photos app. Right now each Article has a photos.photo