Em Sábado 22 Abril 2006 21:07, Alberto Valverde escreveu: > Actually, the best way to accomplish this for *very* large > applications would be to split each component into a separate egg > each team could work independently on. Common services shared between > components will be factored into different eggs too and linked > against when necessary.
Actually, to me, this is the only way to accomplish what the OP wanted. Simply separating packages is not enough and adds nothing to what is there currently and easily done for people that know the basics of Python (i.e. know how to create modules). 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. Kevin's and Alberto's suggestion of using different eggs is much better specially because of how they make it easy to split the application into multiple machines, control dependencies, make components available or not, extend some of TG's features, etc. Fromwhat I've been reading, with First Class the thing will be even better. We achieve something like what it will provide with mod_proxy and separate processes but it isn't just like "attaching" a new part to your system, there's more involved in doing it so it will be really interesting to have a more powerful alternative. Anyway, back to the docs cited on this message, I don't see a difference between the "approaches" indicated since all of them are just creating modules and using them. Different names were given -- controllers, subcontrollers... -- and that's it. I also don't see how it will make it easier to manage access control with any powerful VCS, subversion included of course, since you still have to make the same process of creating modules, importing them, etc. You are even creating another annoying problem: you can't use shortcuts that would allow a more abstract and generic programming by writing the templates like ".templates.my_template" and you'll have to fully qualify it by writing "project.templates.my_template", so reducing how your components can be reused. Anyway, it might just be me and this way of thinking modularly that I have... (If I have a large app then to me there's something wrong since I should have several small apps.) -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
