Theme developers wouldn't *have* to do anything. I'm just talking about an approach to take if they *choose* to do so - for example, if a Theme's users indicate a strong demand for built-in support for a given Plugin.<div>
<br></div><div>Why would you say that it's "hackish" to check for a given Plugin, and supporting that Plugin while providing a graceful fallback - or even a *better* implementation, but deferring to the user's choice? Personally, I do this for two Plugins: Yoast Breadcrumbs and WP PageNavi.</div>
<div><br></div><div>As for a "feature sniffing" approach: that's exactly what if ( function_exists() ) is, and does, quite efficiently. :)</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Sat, Jul 23, 2011 at 7:37 PM, Darren Slatten <span dir="ltr"><<a href="mailto:darrenslatten@gmail.com">darrenslatten@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Chip,<br><br>I'm actually kind of surprised at this suggestion. Doesn't this imply that Theme developers would have to research the plugin repo and determine which plugins' "toes" their Theme needs to avoid stepping on? This doesn't seem practical. Personally, when I see Themes checking for Plugins by name...it seems kind of hack-ish to me. I'm wondering if there's any way we could use a "feature sniffing" approach instead? Or possibly some type of "order of operations" convention.<br>
<br>It seems like a related issue here is the hook priority system. Maybe the current number system is too arbitrary; maybe we should segment the number line into specific uses or something.<div><div></div><div class="h5">
<br><br><br><br><div class="gmail_quote">
On Sat, Jul 23, 2011 at 6:08 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Navigation isn't "functionality"; it is UX. Baking breadcrumb navigation into a Theme falls on the correct side of the Theme-Plugin differentiation, AFAIK.<div><br></div><div>If you want to build in support for breadcrumb plugins, you could use function_exists() conditionals. e.g.</div>
<div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>if ( function_exists( 'yoast_breadcrumbs' ) {</div><div> yoast_breadcrumbs();</div><div>} else {</div>
<div> mytheme_breadcrumbs();</div><div>}</div></blockquote><div><br></div><div>That way, if the user enables Yoast Breadcrumbs, the Theme uses that; otherwise, it falls back to your own breadcrumb navigation.</div><div>
<br></div><div><font color="#888888">Chip</font><div><div></div><div><br><br><div class="gmail_quote">On Sat, Jul 23, 2011 at 5:57 PM, Daniel Fenn <span dir="ltr"><<a href="mailto:danielx386@gmail.com" target="_blank">danielx386@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hello all,</div>
<div> </div>
<div>After reading this I'm starting to think that I may be heading off-track with my wordpress theme.</div>
<div> </div>
<div>Otto, are you saying that my breadcrum code that I put in is a doing it wrong all because I just given people no choice in what plugin they use? </div>
<div> </div>
<div>Would adding the option in my next version to turn it off make it a doing it right? Isn't the idea to make a wordpress theme that has some decent features without needing to use plugins? Is it not true that the more plugins that you got installed the slower wordpress will get?<br clear="all">
</div>
<div style="font-family:georgia,serif">Regards,<br><font color="#888888">Daniel Fenn<br></font></div><div><div></div><div>
<div><br><br><img> <img><br><br></div><br><br><br>
<div class="gmail_quote">On Sun, Jul 24, 2011 at 6:51 AM, Tony Crockford <span dir="ltr"><<a href="mailto:tonyc@boldfish.co.uk" target="_blank">tonyc@boldfish.co.uk</a>></span> wrote:<br>
<blockquote style="border-left:#ccc 1px solid;margin:0px 0px 0px 0.8ex;padding-left:1ex" class="gmail_quote"><br><br>Sent from my mobile, so please excuse brevity and / or formatting errors.<br>
<div><br><br>On 23 Jul 2011, at 21:19, Hilary J Holz <<a href="mailto:holz.hilary@gmail.com" target="_blank">holz.hilary@gmail.com</a>> wrote:<br><br>>> It's certainly<br>>> possible for a theme to implement plugin type functionality, but<br>
>> that's usually overkill for a general purpose theme.<br><br></div>I think this is an interesting point. It seems to me that there are themes and "themes" where we might need to have a new name for a theme that provides a distinct off-shoot of functionality to WordPress to make it fit a particular role.<br>
<br>Perhaps a means to bundle plugins with a theme as a *customising package* might be a better approach?<br><br>I can get behind theme as presentation layer and plugin to add function but there's clearly an overlap where a *theme* needs to add function and style/present it at the same time. I think the lack of a *plugin required* system is what leads to theme authors including plugin type function in theme templates.<br>
<br>Or I might be off the mark.<br>
<div>
<div></div>
<div><br><br>_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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><br clear="all"><br></div></div>-- <br><font color="#888888">Darren Slatten<br><br>
</font><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></div>