> At PyCon, some of us experimented with a full plugin system (Zope > Component Architecture) as used in repoze.BFG. It's too early to tell > whether it would be feasable for a Pylons-like framework (and most of > the developers are too busy to pursue it right now). But the > theoretical idea would be to move some of the middleware to it, use it > for part of Pylons internal configuration and environment.py, and > perhaps expose it to the application developer for customization. And > this may in turn allow for greater interoperability between Pylons, > TG, BFG, and other external software, and simplify the configuration > systems that they all use. (Deployment configuration a la > development.ini would remain separate, maybe, depending on the > framework developer's/application developer's desire.) >
FWIW, I'm one user who things that would be hella cool. I would love see more Pylons/TG/Repoze interoperability and be able us more Zope technology or approaches for projects that get big. =) Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
