I've been having some luck using Trac's component architecture to create plugins for my pylons project. Each plugin is installed using easy_install, and registers itself with a certain entry point name, which is discovered by the pylons app during startup. I have
- a Component which adds new directories to the genshi search path for templates, - one which can find the new controllers to service the request, and adds them to the routes mapper so all routing is still done from routing.py, - another which allows you to define new SQLAlchemy model stuff, and it's all found and loaded together (if you need that), - and a couple others I can't think of right now It's working out pretty well, but it's a bit messy in places. I started blogging about it on http://brennantodd.com - but I've been much too lazy to do any more than the one post from a few months ago. As mentioned by others above, I have one package which contains the majority of my business logic (models, library functions, etc) which is not a Pylons project. Then my pylons site imports from that core package where necessary, and just loads things through the plugin system in other places. Other plugins depend on that core package, but any additional models/views/controllers they provide are discovered by the pylons app through the component system automatically. This is why I haven't blogged any more about this - I'm not sure I make any sense... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
