I am wondering what the 'best practice' is for my current problem, which is basically using someone else's work but keeping it isolated from my own.
I am building a site that needs an "event calender." Justin Lilly has done something similar and gave me http://justinlilly.no-ip.org/svn/trunk/gtd/ Much of that I want to use, but now I am faced with how to integrate it with my project. easy way: grab the source, copy the needed files into my project dir and never look back. In general, I don't like this approach. It forks code that is complex enough that dealing with updates (made to either branch) would be a pain that I don't want to deal with. I plan on adding some things that probably aren't wanted in the generic version (like attaching files to events) but also plan on adding some things that i'm guessing he would want (3x4 table of small months, week view, etc.) This is sounding like a CMS, and maybe it is, but I am not trying to build another Joomla, at least I don't think I am. my hope is that I can use settings .py to manage the various components, and each one can live in it's own dir and be svn updated without any collisions. my files may reference the alien components by subclassing the models and views or extending templates. The hope is these things can be will grow into a site like http://www.djangosnippets.org and http://www.djangosites.org Carl K --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
