I've spent the last few days looking intently at both Django and TG. I haven't yet built anything useful in either, but i've poked at them enough that I think I'm beginning to see through the fog, however dimly.
I'm turbogears only so my comment doesn't counts for Django, in fact i learn about it after so people people talk here about comparing those.
as of today, TG is not great at handling diferent apps in the same server in the sence that totally diferent apps will run together without problems.
now based on what your saying this is not the case here, so it seems you may as well go with it. first of all the basic quickstart template is just a guide, you can turn view and controllers into packages ( and packages inside them) just by moving stuff around (check the tgbig template), same with model but I think you need to do more then just change a config line. but it's simple.
for having a "complex layout" you have both the class/instance structure to generate paths, and for more advance usage like this you will like cherrypy.tree, here is the link http://docs.cherrypy.org/api-reference#tree but for some reason it seems that the docs are down at the moment so google for "cherrypy tree" and see the cache http://tinyurl.com/ofsxa
the *biggest* problem right now is the DB, there is no way to tell TG to go to more then one db, unless you duplicate efforts (http://trac.turbogears.org/turbogears/wiki/MultipleDatabases ) which isn't the prettiest thing right now.
hope that helps.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears
-~----------~----~----~----~------~----~------~--~---
