One of the big advantages of registering and enqueueing is that doing so allows for Child Themes or Plugins to *dequeue*, or *deregister*. It also allows for declaration of dependencies (for scripts), or adding IE conditionals (for styles), and facilitates versioning, among other things.<div>
<br></div><div>Chip<br><br><div class="gmail_quote">On Fri, Jul 15, 2011 at 10:54 AM, esmi at quirm dot net <span dir="ltr"><<a href="mailto:esmi@quirm.net">esmi@quirm.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
on 14/07/2011 13:14 Chip Bennett said the following:<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Those scripts look fine to include; however, you will need to register and<br>
enqueue them properly, using wp_register_script() and wp_enqueue_script(),<br>
via a function hooked into the wp_enqueue_scripts hook.<br>
</blockquote>
<br></div>
[Playing catch-up]<br>
<br>
This brings up a question that I'm pretty sure remained unanswered on the support forums. Is there any benefit to going through the full register then enqueue for a script compared to just dropping everything into an enqueue? Both methods seem to have equal weight in the Codex.<br>
<br>
Mel<div><div></div><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</div></div></blockquote></div><br></div>