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.
My plan for the next six months is to create 4-6 substantial Web applications which will all be variations on a single theme. IOW, I anticipate lots of code and component reuse. Each of the apps will have common core functionality, some additional bells & whistles (on the order of 20% of the total code), and fairly commonly shared user experiences with different looks supplied presumably by the judicious use of CSS.
As I compare these two products with this in mind, it *seems* to me that I'd be better off with Django because of the way its structure seems to lend itself well to the development and deployment of multiple sites in a common code base. Am I right in drawing this conclusion? If not, perhaps someone would be kind enough to explain or point out in the docs how I could adapt TG to accomplish the same task without resorting to code copy-paste.
The second major factor in my design is the need for AJAX componentry and in that regard, at least, it *seems* TG has a strong upper hand, though it could clearly be implemented with some effort in Django.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Shafer, Information Product Consultant and Author
http://www.shafermedia.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
- [TurboGears] Multiple Sites is Driving Factor Dan Shafer
