Rather than the structure you suggest, it might be better to think about your exhibition projects not as django projects, but as django apps. Replace pyA and pyB with root/pyA and root/pyB (e.g. make your php directories a peer of the django root...conceptually, of course...you're Python files won't live physically next to your php files, or shouldn't anyway) and control all your django urls through your urls.py file. This would cut down on the duplication you'd probably end up with in the settings.py file, etc...
I don't mix PHP with Python, but I do mix PHP with Java in the enterprise and there is, IMHO, no inherent conflict in mixing PHP with anything else. There is some duplication (and will be until you're using a single language), but you can generally keep that to a minimum by using an OO approach on both sides. It does create some internal strife in your mind, though, as you switch between worlds. Use the Force, though, and everything will magically turn out all right. ;) Thanks! Jon Brisibn http://jbrisbin.com On Jul 15, 2008, at 4:41 PM, garycannone wrote: > > I have what is a very naive question though I didn't find a close > enough post that answered what I think is a very general question. > > I work at a museum and inherited a site done in php (the coding is > very problematic but this is not the issue). I will overhaul the site > and would like to use Python and Django (I am being asked to make > small desktop apps and collective intelligence type interactions so I > would rather use a general purpose language across the board <py> > suited for all needs). > > (I have used codeIgniter in php for other projects but the site I > inherited uses no php framework) > > Having never used django or mixed languages on a site, I wonder if > there's a way for me to maintain some of the folders I have on the > site while using the django framework? These are exhibition websites > in their own folders > > so I would like the following > > root(django) > |_ folder pyA (containg py files) .. I use the term "folder," but > know it is controller/view > |_ folder pyB (containg py files) > |_ folder a (containing php files).. Existing folder on site > |_ folder b (containing php files)..existing folder on site > > Mind you, I don't want to mix the languages at all in single files. > > I would prefer to use Python, yet would not be able to redo all the > smaller exhibition sites > > My question is, would there be an issue in setting up a structure like > above or should I face facts and realize that the site has to continue > with php in order to maintain everything integrated? > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
