<div class="gmail_quote">On Thu, Sep 2, 2010 at 11:23 AM, Ryan Hellyer <span dir="ltr"><<a href="mailto:ryan@pixopoint.com">ryan@pixopoint.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">>> That "Food Recipe" is the header logo. The Theme gives<br>
>> instructions for how to change it. Thus, it would seem that<br>
>> the developer intends for it to be customizable.<br>
<br>
</div>I don't think that should matter. If the theme developer doesn't want<br>
their end-users having to have a custom header link in their theme,<br>
they shouldn't have to IMO.<br></blockquote><div><br></div><div>Ryan, the developer is <b><font class="Apple-style-span" color="#FF0000">GIVING INSTRUCTIONS FOR CUSTOMIZING THE LOGO</font></b>. Clearly, and obviously, the developer is <b><font class="Apple-style-span" color="#FF0000">INTENDING </font></b>for the log to be customized. What part of that is getting lost in translation? We're not talking about a Theme that doesn't incorporate a customizable logo. If that were the case, this thread wouldn't even exist.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
I made a site for someone last night for example, and changed the<br>
header image for them. There's no way I would have chosen a theme<br>
which had a customisable header image as that would have required me<br>
having to go in and mess around ripping stuff out of the theme. It's a<br>
pain in the neck and a time sink just to do something simple like<br>
remove an image when all I needed to do in the theme I chose was to<br>
change a single image.<br></blockquote><div><br></div><div>Fair enough, but entirely irrelevant. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
By forcing inane requirements on people you are stifling innovation<br>
and making it awkward to create the themes people want. Best to let<br>
theme developers create the theme they intended for their end-users,<br>
not the one that fits a rigid set of arbitrary rules.</blockquote><div><br></div><div>I call shenanigans. </div><div><br></div><div>How is it an inane requirement? The theme developer clearly intends for the end user to customize the logo. WordPress provides handy functionality to allow the user an easy way to upload and use custom logos. Users have a reasonable expectation that Themes downloaded from the repository, that incorporate core features such as customizable header images, should implement such features in a standard, consistent manner.</div>
<div><br></div><div>How is it stifling innovation? Again: the theme developer clearly intends for the end user to customize the logo. Pulling out the "stifling innovation" canard for circumstances such as this is a specious - nay, B.S. - argument, and I'm frankly tired of hearing it.</div>
</div><br><div>How is the guideline in question either rigid or arbitrary? Theme developers <b>are not required</b> to incorporate customizable header logos. But if <b>they choose to incorporate them</b>, they must implement the core functionality, in order to provide a consistent user experience.</div>
<div><br></div><div>Chip</div>