"Requiring" Child Theme is not really a logical construct.<div><br></div><div>Of course, I'd love to *allow* Child Themes, but that's a different discussion entirely. :)</div><div><br></div><div>Chip<br><br>
<div class="gmail_quote">On Fri, Aug 20, 2010 at 8:49 PM, 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">Not if you use another core method of
implementation, a Child Theme.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">So we're going to require child themes now, cause
its a convience?</font></div>
<blockquote style="border-left:#000000 2px solid;padding-left:5px;padding-right:0px;margin-left:5px;margin-right:0px" dir="ltr"><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="philip@frumph.net" href="mailto:philip@frumph.net" target="_blank">Philip M. Hofer (Frumph)</a> </div>
<div style="font:10pt arial"><b>Cc:</b> <a title="edward.caissie@gmail.com" href="mailto:edward.caissie@gmail.com" target="_blank">Edward Caissie</a> ; <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 class="im"><div style="font:10pt arial"><b>Sent:</b> Friday, August 20, 2010 6:46
PM</div>
<div style="font:10pt arial"><b>Subject:</b> Re: [theme-reviewers] Theme
Review Codex Page</div>
<div><br></div>
</div><div><div></div><div class="h5"><div class="gmail_quote">On Fri, Aug 20, 2010 at 8:42 PM, Philip M. Hofer
(Frumph) <span dir="ltr"><<a href="mailto:philip@frumph.net" target="_blank">philip@frumph.net</a>></span> wrote:<br>
<blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote">
<div bgcolor="#ffffff">
<div><font size="2" face="Arial">Not really a devil's advocate type of question
really. There's no evil side to any of the must or
optional.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">Devil's advocate to your devil's advocate then,
the optional searchform.php, what would be the harm in requiring
it?</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">.. because it doesn't need it.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">The end user can edit the style.css via the
appearance -> editor, just like the developer can use get_search_form();
and get the default one that imo is better.</font></div>
<div><font size="2" face="Arial"></font> </div></div></blockquote>
<div>The default search form can also be added via sidebar Widget. It requires
no editing of Theme "core" files. So, searchform.php is truly
superfluous.</div>
<div><br></div>
<div>Conversely, changing the background color does require editing a Theme
"core" file, and is therefore not forward-compatible. </div>
<div><br></div>
<div>Chip</div></div></div></div></blockquote></div>
</blockquote></div><br></div>