<br><br><div class="gmail_quote">On Wed, Jul 7, 2010 at 10:22 AM, Bruce Wampler <span dir="ltr"><<a href="mailto:brucewampler@gmail.com">brucewampler@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;">
Of course, since all themes approved here must be GPL, any parent<br>
must remain available to meet the license. Given that, the best solution<br>
for child themes may remain the one I used for 2010 Weaver - include<br>
the source for the parent with the child theme. Given the rules followed<br>
when running a child theme, it is very easy to "simulate" this simply by<br>
renaming the parent's functions.php and style.css, then include them<br>
explicitly from the child's equivalents, and then keeping or replacing<br>
other parent files as needed. There are some issues with the translation<br>
directory that might complicate this (can there be two translation<br>
directories - parent theme + child theme - in the same theme directory?).<br></blockquote><div><br>There's a potential problem with including the parent theme in a child theme download: If I have two child themes, both with the same parent - but using different versions - the version of the parent theme installed will be the one that came with the most recently installed child. If the other child is not compatible with that version, there's a potential problem.<br>
<br>Could we insist on parent theme version checking in the child themes? At least if there's a non-compatible parent theme, activating the child theme will not cause catastrophic failure. I think if we provide some sample code on how to do that it wouldn't be too much to ask for.<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
And of course, there is still the feature check - is it possible to check<br>
for Gravatar support (for example) in the parent, and then assume<br>
the child thus has it, too?<br></blockquote><div><br>Just because a feature, like Gravatars, is supported in the parent doesn't mean it would not be overridden or removed in the child. I think each item would have to be checked individually in the child theme to determine if it's available and properly implemented.<br>
<br>I agree that allowing child themes in the repository is a great idea.
But it will have to be handled carefully. <br><br>Dave</div></div>