> Sincerely my opinion is the same as it was by the time this discussion > started: this solution pointed out (actually compiled from the archives) > makes it the same as what we have with a default project. Importing will > still be done, everything will be run under the same process / threads, etc.
If you want to scale your project the only way to do it is to use multiple eggs - thats a no brainer. But if you want to split your project into a heirarchy of multiple controllers and templates , so it resembles the division of labor that most webapp people are used to - your options are the big template or one of the other approaches i listed in the wiki. All I'm trying to do is find ways to make TG work with the approaches that non-python people have, so its easier to use for me, and so that more people will adopt it so it doesn't disappear off the face of the earth. The approach that TG has is wholly different from just about every other Framework and webapp design out there. Elsewhere in Python , Django has everything compartmentalized in hierarchical directories. Rails operates simlar. In perl Template Toolkit , Mason, and Embperl are all hierarchical. PHP is usually same thing. But then in TG there's this very pythonic way of tossing everything into as few directories as possible. From the seasoned python programmer's point of view, thats a convenice, and you get a bunch of benefits. From any other perspective, its the number one reason not to use the framework. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
