> 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.
This is, in fact, what I have done with my content management system. The
base management system and few "root-level" components (Atom, Page, Folder,
File, and RootController) appear in the 'content' package, and additional
component collections (like a shopping cart) appear in separate packages.
(The CMS also links itself in with TG for startup and shutdown notification.)
Only strange element in this set-up is that you descend your app's root from
the CMS's RootController, not TG's.
from content.controllers import RootController
class Root(RootController):
pass
My CMS likes taking over your site... ;D
- Matthew
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
