True ... and not wanting to de-rail this thread any further (*grin*) ... this is potentially a (new) discussion thread that could be on par with child-themes as it is very closely related as I see it.<br><br><br>Cais.<br><br>
<div class="gmail_quote">On Thu, Sep 2, 2010 at 11:50 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div class="im">On Thu, Sep 2, 2010 at 10:42 AM, 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: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Thanks Chris ...<br><br>"Framework" themes are a whole different animal than most themes ... and some tend to do things out of the ordinary.<br><br>I'll post some questions, here:<br><ul><li>Should they be handled differently?</li>
<li>Should we add additonal Trac keywords?<br></li><li>Should there be an assignable tag by the Review team so they enter/exist in the repository with more recognition of their inherent potential and options?</li></ul>Just some thoughts, there are perhaps 10 or so that would come to mind if we took a look at the repository ... the Carrington themes, Thematic, Hybrid, ComicPress, Suffusion, Atahualpa, Tarski, etc come to mind off the top of my head, I know there are more.<br>
<br>"Framework" may not be the most appropriate term, but these themes et al. represent the ones that have a great many available options, for example, that are well above and beyond most.<br></blockquote><div>
<br></div></div><div>I would go with Justin Tadlock's nomenclature with respect to "frameworks" - that is, drop-in code on top of which Parent Themes are built. In Carrington's case, this drop-in code is "Carrington Core". I believe Thematic and Hybrid are (or will be?) much the same.</div>
<div><br></div><div>My thinking is that we really need first to review/approve the framework code. That way, if a Theme is using a known/approved version of the framework, that part can be ignored in the Theme review.</div>
<div><br></div><div>The question then becomes: how best to handle review/approval of frameworks?</div><div><br></div><font color="#888888"><div>Chip</div></font></div>
<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>