On Mon, Mar 19, 2012 at 11:13 AM, Chris McDonough <[email protected]> wrote: > Talking about "plugin systems" is probably overeager here. I think what > Lukasz may need to do is to enumerate the goals implied by his use of > the term "plugin system" and maybe describe one (read: not all!) of > those goals in concrete detail so we can provide an example of how he > might accomplish it using the existing machinery.
Still, it's a frequently-asked question. People often ask for "plugins", and have wildly different notions of what a plugin is, based on the terminology of other frameworks and languages. So ideally we'd have an article that lists all the different kinds of plugins, which ones apply to Pyramid, what kinds of use cases they cover, and how to do them. Is there anyone familiar with a lot of plugin patterns who could outline them, and specify which ones have a Pyramid equivalent? -- Mike Orr <[email protected]> -- 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.
