<div dir="ltr">> <span style="font-family:arial,sans-serif;font-size:13px">And until declaring support for it does something</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">more than just adding a menu, I doubt it's meaningful enough to need a</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">theme_support option that would have to be supported by core for the</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">foreseeable future.</span><div>
<span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div style><span style="font-family:arial,sans-serif;font-size:13px">This is the main part I disagree with. There is inherent value in exposing the Customizer to the user with the same efficiency as the Theme Options page.</span></div>
<div style><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div style><span style="font-family:arial,sans-serif;font-size:13px">Theme Options: Dashboard -> Appearance -> Theme Options</span></div>
<div style><span style="font-family:arial,sans-serif;font-size:13px">Customizer: Dashboard -> Themes (if you know to look there) -> (load page) -> Customize</span></div><div style><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div style><span style="font-family:arial,sans-serif;font-size:13px">If Themes are going to add one line of code, isn't it far superior to add a never-needs-to-be-changed add_theme_support() call, than to add a different bit of code, that could potentially change in the future?</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 4, 2013 at 11:01 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.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">On Mon, Mar 4, 2013 at 9:48 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> So what about an add_theme_support() option, for Themes that opt to<br>
> integrate options into the customizer?<br>
<br>
</div>What would declaring theme support for the customizer even do? If it's<br>
just adding the menu option, heck, themes can do that themselves with<br>
a single line of code.<br>
<br>
There's no point in having yet-another theme_support system until it<br>
does something that can be considered a) relatively stable, b)<br>
meaningful, and c) likely to expand in scope in the future. The<br>
customizer is likely to expand, but I wouldn't call it "stable" yet,<br>
since even the controls changed somewhat in 3.5 and will probably<br>
change more in 3.6. And until declaring support for it does something<br>
more than just adding a menu, I doubt it's meaningful enough to need a<br>
theme_support option that would have to be supported by core for the<br>
foreseeable future.<br>
<br>
Maybe eventually. But again, it's not there yet.<br>
<div class="HOEnZb"><div class="h5"><br>
-Otto<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>
</div></div></blockquote></div><br></div>