That's a good practice, I will follow that from now.<br>
<br><br><div class="gmail_quote">On Thu, Mar 3, 2011 at 6:17 PM, Rahul Bansal <span dir="ltr"><<a href="mailto:rahul.bansal@rtcamp.com">rahul.bansal@rtcamp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
As part of our internal coding standard... all CSS & JS are registered at once and then enqueued as need arises (like in conditional statement, etc)<div><div><div><br><div>--<br>Rahul Bansal | Founder & CEO | rtCamp Solutions Pvt. Ltd.<br>
Skype: rahul286 | Twitter: @rahul286 | Web: <a href="http://rtcamp.com/" target="_blank">http://rtcamp.com/</a><br><br>
<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Sun, Feb 27, 2011 at 6:40 PM, Satish Gandham <span dir="ltr"><<a href="mailto:satish.iitg@gmail.com" target="_blank">satish.iitg@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5">
Why should we register styles before using wp_enque() , when we can directly add the style sheet path and name using enque?<br><br>Is it to allow child themes to override ?<br><font color="#888888"><br><br><br>Satish Gandham<br>
<br><br><br><br>
<br><br>
</font><br></div></div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div></div></div></div>
</blockquote></div><br>