On Apr 17, 8:26 pm, "Dave Dash" <[EMAIL PROTECTED]> wrote: > How do we extend plugins beyond their solitary uses? > > ... > > For the task at hand I am in favor of plugins that depend on other plugins > for the meantime, I just hope that doesn't get to become too unwieldy ;) >
François suggested using sfMixer and callbacks for add-ons for his blog plugin and that would seem to be a sensible way to go for that sort of functionality. A sensible and consistent naming scheme would be useful for plugins of plugins, eg sfGuardForgotPasswordPlugin. Mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
