<!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>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 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=philip@frumph.net
href="mailto:philip@frumph.net">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">Edward Caissie</A> ; <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> 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 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">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></BLOCKQUOTE></BODY></HTML>