<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928">
<STYLE></STYLE>
</HEAD>
<BODY 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 style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=chip@chipbennett.net href="mailto:chip@chipbennett.net">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">theme-reviewers@lists.wordpress.org</A>
</DIV>
<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">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 class=h5><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">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>
<P>
<HR>
<P></P>_______________________________________________<BR>theme-reviewers
mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></BLOCKQUOTE></BODY></HTML>