[wp-hackers] wp_register_script() vs. wp_enqueue_script()?

Mike Schinkel mikeschinkel at newclarity.net
Tue Jan 27 17:09:55 GMT 2009


-Mike Schinkel

----- Original Message -----
From: "Jeremy Clarke" <jer-wphackers at simianuprising.com>
To: wp-hackers at lists.automattic.com
Sent: Tuesday, January 27, 2009 11:15:51 AM GMT -05:00 US/Canada Eastern
Subject: Re: Re : Re: [wp-hackers] wp_register_script() vs.  wp_enqueue_script()?

It would indeed be nice to have one comprehensive list of things you
should do when writing a plugin. That coding standards page is more
about the formatting you should use when creating patches to core,
rather than any actual API stuff you should be using for plugins.

This new page could take the format of basically a list of APIs that
people should be using to accomplish various tasks along with links to
api description pages (like Settings API or Widgets API).  Then it
would be a good way for experienced coders to go through and make sure
they're not missing any big sections of how WP makes their lives
easier and forward-compatible at the same time.

I think the problem you'll find is the lack of overview pages for many
of the APIs (i wrote ones for the Settings API and Dashboard Widgets
API in the last few days but there are many more i'm sure that could
be added to great utility, especially the new ones added since 2.5, of
which there are many and which are generally pretty awesome).

Maybe this conversation belongs on wp-docs or whatever, but I think
its up to us coders to write our own coding pages if we want them.
It's a great way to acquaint yourself intimately with an API!

Jeremy Clarke | http://simianuprising.com
Code and Design | http://globalvoicesonline.org
wp-hackers mailing list
wp-hackers at lists.automattic.com

More information about the wp-hackers mailing list