If our options are: require, recommended, or optional ... I would lean heavily towards optional.<br><br>If suggested (as noted below) is an available option I would be fine with that designation.<br><br><br>Cais.<br><br><div class="gmail_quote">
On Thu, Jul 15, 2010 at 7:48 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
+1<br>
<br>
(Note: I originally put it in the "must" category - along with everything else<br>
- as a basis to begin discussion. So, I'm glad we're having that discussion!)<br>
<br>
Sounds like a good, convincing argument to me! :)<br>
<br>
But, where to put it? I think our options are "required", "recommended", and<br>
"optional".<br>
<br>
What about "suggested (unless the theme design/layout would be adversely<br>
affected)"?<br>
<br>
If not something along those lines, then I'd say just make it optional.<br>
<font color="#888888"><br>
--<br>
Chip Bennett<br>
<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a><br>
<a href="http://www.chipbennett.net" target="_blank">www.chipbennett.net</a><br>
</font><div><div></div><div class="h5"><br>
On Thursday 15 July 2010 9:38:02 am Edward Caissie wrote:<br>
> I would like to submit back for discussion to the mailing-list/Theme<br>
> Reviewers the "must" requirement of including 'add_custom_header' support<br>
> to themes.<br>
><br>
> The function itself is great and relatively easy to implement but I see it<br>
> as focused for use with single banner style image header areas, such as<br>
> Twenty-Ten and similarly designed themes. This then presents an issue for<br>
> themes that do follow this particular design concept/layout especially<br>
> themes that do not have header images per the author's choice; or, a more<br>
> difficult to address issue of themes with multiple images in the header ...<br>
> again a theme author's choice.<br>
><br>
> Dictating the use of 'add_custom_header' as a _must_ item in theme<br>
> development will start pushing themes to more of a cookie-cutter look and<br>
> feel, not to mention the potential for authors to simply lift the code, for<br>
> example, from Twenty-Ten and drop it into their own theme to meet the must<br>
> need of the requirement. This leads right into originality issues with<br>
> themes as well ... another topic for another thread.<br>
><br>
> As examples, I will use my own themes (currently in the repository) simply<br>
> due to my familiarity with them.<br>
><br>
> 1) Desk Mess Mirrored:<br>
> <a href="http://wordpress.org/extend/themes/desk-mess-mirrored/" target="_blank">http://wordpress.org/extend/themes/desk-mess-mirrored/</a><br>
> - three (3) header images; of which each image I have seen modified<br>
> individually, or with one other ... or in rare cases all three.<br>
><br>
> 2) Shades: <a href="http://wordpress.org/extend/themes/shades/" target="_blank">http://wordpress.org/extend/themes/shades/</a><br>
> - no header image; although 'add_custom_header' should be relatively easy<br>
> and straight forward to implement I envisioned this theme to start with no<br>
> header; and, to allow end-users to modify the header area as they saw fit.<br>
><br>
> 3) Ground Floor: <a href="http://wordpress.org/extend/themes/ground-floor/" target="_blank">http://wordpress.org/extend/themes/ground-floor/</a><br>
> - no distinct header image; this theme has a dynamically expanding header<br>
> area to allow for very long titles, taglines, horizintal top menus etc.<br>
> Implementing 'add_custom_header' would for all intent and purpose break the<br>
> theme's look and feel.<br>
><br>
> 4) NoNa: <a href="http://wordpress.org/extend/themes/nona/" target="_blank">http://wordpress.org/extend/themes/nona/</a><br>
> - a distinct header image that is integral to the theme layout itself. To<br>
> implement 'add_custom_header' for this theme is possible but would require<br>
> a certain level of skill with a graphic program to create additional<br>
> headers. Otherwise it is essentially being dictated the theme itself may<br>
> be required to be re-written and the graphics re-made to meet the<br>
> requirement of adding this function.<br>
><br>
> In my opinion, themes similar to 2) and 3) above would be detrimentally<br>
> affected by the "must" use criteria placed on 'add_custom_header'. Themes<br>
> that follow similarly to 4) above may have limited usability added by the<br>
> addition of the function.<br>
><br>
> Quite honestly I would like to be able to add the function of custom<br>
> headers to Desk Mess Mirrored, but as I wrote at the beginning of this<br>
> message the 'add_custom_header' function does not appear to directly<br>
> handle multiple header images displayed on the same page at the same time;<br>
> and, from what I am able to see in the supporting core code it would<br>
> require a great deal of custom code to add that functionality to the<br>
> theme, or similar themes, in question.<br>
><br>
> I strongly believe the function has a great deal of use and potential, but<br>
> I do not believe it _must_ be included for a theme to be accepted into the<br>
> repository. Perhaps suggested, recommended, or simply optional would be a<br>
> better requirement benchmark.<br>
><br>
><br>
> --<br>
> Edward Caissie<br>
> <a href="http://edwardcaissie.com" target="_blank">http://edwardcaissie.com</a><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>