<div dir="ltr">Thanks to everyone who chimed in.<div><br></div><div style>I will definitely add notes on theme's usage of Customizer Boilerplate before submitting the updated version. </div><div style><br></div><div style>
Also, it's only function prefixes that are different and relevant. There's also an array of sample options in <a href="https://github.com/slobodan/WordPress-Theme-Customizer-Boilerplate/blob/master/customizer-boilerplate/options.php">this file in Customizer Boilerplate</a><span id="goog_1676479741"></span><span id="goog_1676479742"></span><a href="/"></a>, "using" 'my_theme_textdomain' translation string, but those are just sample options and are not meant to be translated, but simply overwriten in themes function.php file.</div>
</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><font size="1"><font face="arial, helvetica, sans-serif">
</font><p style="font-weight:800"><font face="arial, helvetica, sans-serif">---</font></p><p>
</p><p><font face="arial, helvetica, sans-serif"><span style="font-weight:800">Slobodan Manic</span><br>WordPress developer at <a href="http://thematosoup.com/" target="_blank"><font color="#cc0000"><b>ThematoSoup</b></font></a><br>
Twitter: <a href="https://twitter.com/#!/slobodanmanic" target="_blank"><font color="#cc0000"><b>@slobodanmanic</b></font></a></font><br></p><p style="font-family:tahoma,sans-serif"></p></font></div></div>
<br><br><div class="gmail_quote">On Tue, Mar 5, 2013 at 2:32 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The premise behind the namespace guidelines are to help insure a few<br>
things, one being theme uniqueness.<br>
In this case, given the "drop-in" and the theme are by the same<br>
author, the issue of namespace clashing should be moot.<br>
<br>
I would be able to accept this namespace difference, perhaps adding a<br>
note to the theme's documentation explaining the difference /<br>
relevance would be helpful.<br>
<br>
Also, as noted by @Daniel, this issue has already been addressed and<br>
"drop-in" libraries are fine to use, especially since this one appears<br>
to use a unique prefix as its namespace.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
Edward Caissie<br>
aka Cais.<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On Tue, Mar 5, 2013 at 3:21 AM, Abhik Biswas <<a href="mailto:abhik@itsabhik.com">abhik@itsabhik.com</a>> wrote:<br>
> I must have missed that.<br>
><br>
><br>
> On Tue, Mar 5, 2013 at 1:39 PM, Daniel Tara <<a href="mailto:contact@onedesigns.com">contact@onedesigns.com</a>> wrote:<br>
>><br>
>> That is not true. Frameworks are allowed to be used unaltered; that's he<br>
>> whole point of using frameworks anyway. This has been discussed before<br>
>> (several times) and has been deemed acceptable. See here:<br>
>><br>
>> <a href="http://make.wordpress.org/themes/2012/03/14/theme-frameworks-and-namespacing-guidelines/" target="_blank">http://make.wordpress.org/themes/2012/03/14/theme-frameworks-and-namespacing-guidelines/</a><br>
>><br>
>> Daniel<br>
>><br>
>> On Mar 5, 2013, at 8:45 AM, Abhik Biswas wrote:<br>
>><br>
>> As long as I know, themes are *required* to use its name's slug as the<br>
>> callback prefixes. Therefore, if you are using a prefix that's not your<br>
>> theme's name slug, might colide with other callbacks. Also, all the callback<br>
>> prefixes in a theme should be same and unique. You can not use different<br>
>> prefixes in a single theme.<br>
>><br>
>> A veteran reviwer can clarify it better than me.<br>
>><br>
>> _______________________________________________<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>
>><br>
>><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>
><br>
><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>
_______________________________________________<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>