[wp-hackers] Plugin dependency checking

[scribu]

Ok, now I get what you were trying to say with "Interfaces".

Yes, not using interfaces would would limit what could be done with
their children, but on the other hand, interfaces would limit what
child plugins could do themselves. It's a tradeoff.

It's the same tradeoff that would happen if normal plugins would have
to have an interface that the core would have to check.

On 6/16/09, Mike Schinkel <mikeschinkel at newclarity.net> wrote:
> "scribu" <scribu at gmail.com> wrote:
>> One or more child plugins can use functionality provided by one
>> parent plugin. Parent plugins are not aware of the additional
>> functionality that each child plugin provides. That's the basic
>> model.
>
> As with discussion with Steven on the list, let me urge not to have the
> child name its parent but instead have the child name the "interface" that
> its parents can consume.  Steven called is "offers" and "uses"; most any
> terms will work but coupling children directly to parents will really limit
> what can be done with their children and IMO would be a mistake.
>
> -Mike Schinkel
> Custom Wordpress Plugins
> http://mikeschinkel.com/custom-wordpress-plugins
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>


-- 
http://scribu.net