<div dir="ltr">There are two issues, separate but related:<div><br></div><div style>1) Plugin dependency</div><div style>2) User experience</div><div style><br></div><div style>Certainly, a Theme must not be *dependent* on a Plugin, including the OF Plugin. However, it is entirely possible to develop a Theme that functions fully without the Plugin, and merely *extends* the Theme by exposing Theme options if the Plugin is installed. (And if Theme options are handled properly, including sane-default fallback values, that's entirely possible.)</div>
<div style><br></div><div style>However, even if a Theme properly handles options such that it functions fully without the Plugin, including options via Plugin still presents a less-than-ideal, or even a bad, user experience. Why should a user have to take the extra time and effort to find, install, and activate a separate Plugin, merely to be able to use an integral Theme feature such as Theme options? I don't view Theme options as an extension of functionality.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 18, 2013 at 12:00 AM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We'd have to look at things on a case-by-case basis. We can't just generalize all libraries/frameworks/scripts. But, in general, I'd argue for inclusion within the theme. This is an approach that I've been using successfully since 2008, so I'm hardly unbiased.<br>
<br>
For the Options Framework in particular, I think it needs to be within the theme. It seems like an integral component to the theme. It's part of what makes a particular theme what it is.<br>
<br>
With that said, I see no issue with a plugin approach as long as the theme functioned correctly without the plugin. As far as I'm concerned, it is an equally valid approach. And, encouraging alternative approaches is something we should do a bit more of within the theme reviewer circle and the larger WP theme community.<div class="HOEnZb">
<div class="h5"><br>
<br>
On 4/17/2013 9:46 PM, Devin Price wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi. I wanted to bring a discussion that Chip and I were having in ticket to the larger group for feedback.<br>
<br>
The question is whether libraries like the "Options Framework" should be bundled directly with the theme or if it's better to use a plugin to enable the functionality.<br>
<br>
I've always considered both approaches equally valid- though I recommend using the plugin version if no modifications are being made to the framework. Arguments for both are represented in the ticket: <a href="http://themes.trac.wordpress.org/ticket/12027" target="_blank">http://themes.trac.wordpress.<u></u>org/ticket/12027</a><br>
<br>
Curious to know what other people think.<br>
<br>
Thanks much,<br>
Devin.<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</div></div></blockquote></div><br></div>