I tend to agree. This Plugin, in particular, is, I think, intended to be *integrated* into a Theme. It serves little to no purpose as a stand-alone Plugin, when it is installed within the context of a Theme that, even if it supports post formats, doesn't support the Plugin's data-entry conventions.<div>
<br></div><div>That said, it can also be considered to be a "code framework", managed/updated separately from the Theme. In such case, I would rather see the Plugin NOT integrated into the Theme at all, but rather treated as a *dependency* of the Theme. This would be my preferred approach, as it would allow the Plugin developer to drive maintenance/development of the Plugin code, separately from the Theme. Thus, my recommendation would be to keep the Plugin separate from the Theme, and instruct end users to install the Plugin as part of the Theme installation/setup. (There are even scripts available for "automating" download/installation of such dependent Plugins.)</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Thu, Feb 23, 2012 at 7:47 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com">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">
My first thoughts on this ...<br><br>... I like the idea of adding functionality; but given the code and how it is written if you are considering this as a drop in bit-to-bit exact copy (off-by-default) then using a call within your theme to activate and use, I would be fine to leave the plugin code as is.<br>
<br>If your intent is to include the code as an "inspiration" to enhance your theme's current functionality in a "on-by-default" manner then I would expect it to be properly prefixed (and internationalized as needed) matching your theme's current conventions ... and, of course, attributed in a suitable fashion, too.<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote"><div><div class="h5">On Wed, Feb 22, 2012 at 9:04 PM, Sayontan Sinha <span dir="ltr"><<a href="mailto:sayontan@gmail.com" target="_blank">sayontan@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">
Hi,<br>I would like to include code from this plugin: <a href="http://alexking.org/blog/2011/10/25/wordpress-post-formats-admin-ui" target="_blank">http://alexking.org/blog/2011/10/25/wordpress-post-formats-admin-ui</a> in my theme because I support a few post formats. I have a few questions in this regard:<br>
<ol><li>Would that be permitted from a functionality point of view (re: plugin functionality vs. theme functionality arguments)?</li><li>If permitted, can I retain the plugin's own prefixes for its functions?</li></ol>
<p>Thanks,<br>Sayontan<span><font color="#888888"><br></font></span></p><span><font color="#888888"><br>-- <br>Sayontan Sinha<br><a href="http://mynethome.net" target="_blank">http://mynethome.net</a> | <a href="http://mynethome.net/blog" target="_blank">http://mynethome.net/blog</a><br>
--<br>
Beating Australia in Cricket is like killing a celebrity. The death gets more coverage than the crime.<br><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>