<!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>True that, but by the same token, there are
'different' methods of implementation.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>custom-background has several different methods
that could be an alternative including the themes own option pages which have a
varity of different sublooks to it which would really faulter.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>My own CommPress theme has a specific background
look to it, that would just make it look silly if someone didnt know what they
were donig and put something else there.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Do you want the end-user to have the ability to
make their sites crap looking visually with ease?</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>of course if you're in it for the money for
supporting clients, then sure .. yeah absolutely. ;/</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>however I digress even though automatic-feed-links
can have the luxury of being hardcoded it's not feasibly responsible of the
theme developer to dismiss having it.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>however, these themes that come in, they're
designed with a look and thats what people are grabbing those themes for, ..
that look. It's a convience not a necessity to require
custom-backgrounds because it changes the overall themes default
representation.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>^ it's all good either way for me, if its a
must-have and someone tells me its a must have then sure, but thats not what I
started asking about, it was post thumbnails.</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Take P2 for example. Would having
post-thumbnails *really* be a must for that theme to have included?
I'm sure it could be utilized sure, but does it 'have' to ?</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"
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:54
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [theme-reviewers] Theme
Review Codex Page</DIV>
<DIV><BR></DIV>"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
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 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></BLOCKQUOTE></BODY></HTML>