[wp-hackers] Child plugins (add-ons)
almog.baku at gmail.com
Sat Feb 16 11:19:21 UTC 2013
By my opinion the properly solution is to implement a *Dependency system*.
and and the ability to plugin requiring another pluging.
On Fri, Feb 15, 2013 at 9:26 PM, Dino Termini <dino at duechiacchiere.it>wrote:
> Hi Marko,
> WP SlimStat already includes a number of actions and hooks that allow
> third-party developers to extend its functionality. A "separate plugin that
> needs the main..." is just one way of looking at things. If we apply your
> reasoning to Child Themes, then that naming is "wrong" as well, as they are
> usually extensions or customizations of existing themes, and not separate
> themes relying on their parents ;) But naming conventions aside, I believe
> it would be great to expand the Plugins Management interface to group
> (accordions?) plugins based on their relationships. I haven't looked at the
> way BuddyPress implements it, but it could be a good starting point.
> On 2/15/2013 2:14 PM, Marko Heijnen wrote:
>> Hey Dino,
>> If it is a part of your plugin then delete doesn't make sense. Just an
>> option to make it active or not. The word 'Child plugin' would be wrong for
>> A 'Child plugin' for me would be a separate plugin that needs the main
>> plugin because it uses the hook the main plugin has. Like a random
>> BuddyPress plugin that obviously need BuddyPress.
>> So I guess you should look into your plugin and see if there are places
>> where it make sense to add an action or a filter.
> wp-hackers mailing list
> wp-hackers at lists.automattic.**com <wp-hackers at lists.automattic.com>
More information about the wp-hackers