[wp-hackers] Strider Core (was Need help with: coding new Plugin options)

Stephen Rider wp-hackers at striderweb.com
Sat Nov 8 01:38:40 GMT 2008

On Nov 7, 2008, at 2:13 AM, Daiv Mowbray wrote:

> After reading numerous plugins, trying to determine what is the best  
> practice for writing a plugin, I have learnt that there is no  
> standard.
> It seams that every one does it different from the next.
> ...
> A plugin template would be a great tool for standardizing.
> I have found suggestions such as the following, which I think are  
> great ideas:

> [cited plugin action links and plugin page footer attribution]

I see you've been reading my articles... ;)

I'm actually working on a common code "back end" that I plan in  
incorporating into all of my plugins.  It includes common code for  
exactly the kinds of things you mentioned, plus things like a system  
for updating plugin options on plugin update -- e.g. with defaults for  
settings that didn't exist in the previous version of the plugin --  
and hopefully an automatic Version Checking mechanism for plugins not  
hosted at WP-Extend.

I've dubbed it "Strider Core".  I think the most interesting things  
about it is that I've figured out a way so that if multiple plugins  
all use Strider Core, it will check for the _newest_ version of SC and  
use that for all of those plugins.  Thus, updating one plugin can  
improve other plugins running on the same base code.  (Example:  If  
Plugin A has SC v1.0, and Plugin B has SC v1.1, both plugins will run  
on SC v1.1)

The first public release running on Strider Core is probably going to  
be a new version of my "Deprecated Calls" plugin.  It's certainly not  
going to be all things to all plugin authors, but it will encapsulate  
and (hopefully) standardize a lot of the bits of polish that can  
improve all plugins.

I'll keep y'all posted. :)


Stephen Rider

More information about the wp-hackers mailing list