Re: Plugin architecture

[Ben Bangert]

On Apr 28, 2009, at 2:43 PM, Wichert Akkerman wrote:

If you decide to use zope.component a controller could be a named
utility. You could then register it like so:

 class BaseController(object):
     """This is the standard Pylons base controller class."""
     implements(IPylonsController)


 class MyController(BaseController):
     """My very own controller."""

 registerUtility(MyController, name="my_controller")

Yikes! :)





Cheers,
Ben

I was trying to only include interfaces enough such that an end user would never have to see them but they'd be helpful to allow/encourage plug-ins. The second a Pylons developer has to start knowing interfaces, utilities, registering things *just* to get the basic app working, Pylons has lost something I think is very important. I was aiming for any potential use of the zope stuff purely for use with plug-ins, or changing core aspects of Pylons that are currently difficult to tweak. Though its definitely true that even making a small basic app might involve an extra step to allow for pluggability.

smime.p7s
Description: S/MIME cryptographic signature