I agree with appropriate use of template tags, especially get_template_ vs get_stylesheet_, but I think that's in line with our current Guidelines (and something that's already being enforced in recent tickets).<div>
<br></div><div>Perhaps that needs to be expounded/clarified in the Guidelines, though?</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Sat, Jan 22, 2011 at 11:15 AM, Philip M. Hofer (Frumph) <span dir="ltr"><<a href="mailto:philip@frumph.net">philip@frumph.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff">
<div><font size="2" face="Arial">I agree with the child-ready themes and I think
that's the jist of what Otto was saying, making sure things like get_stylesheet_
and get_template_ were used properly and such.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial"></font> </div>
<div> </div>
<blockquote style="border-left:#000000 2px solid;padding-left:5px;padding-right:0px;margin-left:5px;margin-right:0px"><div class="im">
<div style="font:10pt arial">----- Original Message ----- </div>
<div style="font:10pt arial;background:#e4e4e4"><b>From:</b>
<a title="chip@chipbennett.net" href="mailto:chip@chipbennett.net" target="_blank">Chip
Bennett</a> </div>
<div style="font:10pt arial"><b>To:</b> <a title="theme-reviewers@lists.wordpress.org" href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
</div>
</div><div><div></div><div class="h5"><div style="font:10pt arial"><b>Sent:</b> Saturday, January 22, 2011 9:12
AM</div>
<div style="font:10pt arial"><b>Subject:</b> Re: [theme-reviewers] Child
themes discussion</div>
<div><br></div>*Any* stand-alone Theme can act as a Parent Theme.
<div><br></div>
<div>I hesitate to force Theme developers to facilitate/accommodate
pluggable/hookable Child Theming. If they choose to do so, that's another
matter, but we should not be *forcing* Theme developers to make all of their
custom Theme functions pluggable ( ! function_exists() wrappers) or hookable.
<div><br></div>
<div>Perhaps a better implementation here would be to find a
positive-reinforcement means to encourage child-ready Themes?</div>
<div><br></div>
<div>Chip<br><br>
<div class="gmail_quote">On Sat, Jan 22, 2011 at 11:04 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span>
wrote:<br>
<blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote">I would say if the addition to 7) is added then the
addition to 6) would less of a requirement to insure a theme is
"child-able". Although best-practice coding is always a good thing to
recommend.<br><br><br>Cais.
<div>
<div></div>
<div><br><br>
<div class="gmail_quote">On Sat, Jan 22, 2011 at 11:49 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br>
<blockquote style="border-left:rgb(204,204,204) 1px solid;margin:0pt 0pt 0pt 0.8ex;padding-left:1ex" class="gmail_quote">
<div>> 6) (if) a functions.php exists, it must be compatible with the
latest<br>> version of the parent theme<br><br></div>On this note, it
might be a good idea to start suggesting that all<br>themes with
functions.php files be child-able. By this, I mean that<br>everything in
the functions.php should be in a hooked function or have<br>a if !defined
/ !function_exists wrapper around it. Some best<br>practices could be
drawn up.<br>
<div><br>> 7) (if) parent theme is updated, all child themes must be
updated within a<br>> reasonable amount of time to fit with the current
parent if applicable ?<br><br></div>That a reasonable question: How to
handle breakage. Parents can make<br>radical changes that will break
children. Maybe create a list of<br>themes that are "designed to be
parents"?
Dunno.</blockquote></div><br></div></div><br>_______________________________________________<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><p>
</p><hr><div class="im">
<p></p>_______________________________________________<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>
</div><p></p></blockquote></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">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>