The general namespace Guideline has never been interpreted as rigidly as the textdomain Guideline. This is a slightly subjective area, and can usually be resolved between Theme developer and reviewer.<div><br></div><div>The Guidelines were recently updated to clarify the purpose/intent for enforcement of the namespace Guideline. Please let me know if it is still ambiguous.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Thu, Sep 6, 2012 at 12:16 PM, Shinra Web Holdings <span dir="ltr"><<a href="mailto:shinrawebholdings@gmail.com" target="_blank">shinrawebholdings@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 problem is if you're using the same slugs in more than one project you run the risk of defining functions twice, which will break PHP. You could prefix every function with if( !function_exists( 'sameslug_function_name ) ), but then you just end up typing more, not less. On top of that you risk older versions of those functions being run expecting newer results, or running a completely unrelated function that's in your namespace improperly.<br>
<br>If you really have to reuse code, I guess the safest way would be to put it in a custom class and do a version check each time you create an instance. <br><br><br><br><div class="gmail_quote"><div><div class="h5">On Thu, Sep 6, 2012 at 12:00 PM, Bruce Wampler <span dir="ltr"><<a href="mailto:weavertheme@gmail.com" target="_blank">weavertheme@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">I have a question about using the theme slug. One of the important goals of the slug is to create a "namespace" for the theme, and as far as I know, the interpretation has been to have every theme use its slug on all names. But this brings up an issue.<br>
<br>I have an existing theme (Weaver II) and its slug 'weaver-ii'. It is a large theme, and has lots of support functions.<br><br>I'm now thinking about developing a smaller version of the theme - called Weaver Mini, perhaps. Now, since I "own" the slug 'weaver-ii', would it be acceptable to reuse all that support code in the new theme (slug 'weaver-mini') while keeping the 'weaver-ii' name for the support code. Would make maintenance a lot easier, and it seems it preserves the intent of the theme slug rule. <br>
<br>Seems like a general policy on this could be really helpful for lots of theme developers who reuse code. Might even want to extend it to allow re-use of other theme libraries. I suspect there is code in my theme's support code that could be useful in other themes, and allowing reuse of my slug in other themes would help maintenance issues for sure. Since only one theme is active at a time, this seems like a safe way to preserve namespaces.<span><font color="#888888"><br>
<br>Bruce Wampler<br>
</font></span><br></div></div>_______________________________________________<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>_______________________________________________<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>