[wp-hackers] What Should A Plugin Author Do To Make Plugins Extensible?
rbilesky at gmail.com
Tue Aug 31 04:12:01 UTC 2010
idk that enough plugin use this to make it worthwhile to include such a
section. Plugin authors can always put API documentation under "Other
On Mon, Aug 30, 2010 at 2:08 PM, Mike Schinkel
<mikeschinkel at newclarity.net>wrote:
> It would be nice in the plugin page had a separate section label API to
> encourage more plugin developers to think about including an API and to give
> other developers an easy place to look for API docs. JWTCW.
> On Aug 30, 2010, at 4:58 PM, Jeremy Clarke <jer at simianuprising.com> wrote:
> > On Mon, Aug 30, 2010 at 12:12 AM, Andrew Nacin <wp at andrewnacin.com>
> >> - Wrap functions in function_exists(). Not necessary for functions
> >> attached
> >> to hooks as those can be removed, or those where overriding them makes
> >> little sense (unless you want to be sure there are no conflicts... It's
> >> good
> >> practice).
> >> - Include actions and filters of your own.
> > And *mention the new actions/filters/pluggable-functions that you've
> > in your plugin description*. If you don't mention them then developers
> > know they are there and will be less likely to choose your plugin because
> > they don't realize that you're doing extra work to make their lives
> > IMHO this even applies to template tags and helper functions. I think a
> > more functions from plugins are worth mentioning on the plugin page and
> > treating as a kind of API. If nothing else it would encourage plugin devs
> > think of their functions as an API rather than something only they use,
> > which might increase usability for others.
> > --
> > Jeremy Clarke
> > Code and Design | globalvoicesonline.org
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers