> It seems like TG makes modular design > pretty much impossible, you can't build an application and then > package up add-ons and skins that people could install without hacking > code, at least not easily. That to me seems like a major hurdle to > adoption depending on what you're doing.
I don't think this is true. Our problem is that we haven't created the "one right way" to do any of this stuff, and we haven't documented the myriad ways that it can be done now, so it seems less promising than Django, but really it's not. You can create TG plugins using setuptools and entry points, you can skin things using conditional xincludes in genshi, or by adding something like Deliverance middleware to your stack (allowing you to compose apps into a unified site and skin it all even if the components aren't all python apps). And the Django way of doing reusable component apps requires at least a little bit of hacking code if I'm not mistaken. So, I don't think the two are as far apart as it looks. It's just a matter of documentation and of making some decisions about the "right" way to tell people to do this. --Mark --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
