[theme-reviewers] Child themes discussion

[Chip Bennett]

*Any* stand-alone Theme can act as a Parent Theme.

I hesitate to force Theme developers to facilitate/accommodate
pluggable/hookable Child Theming. If they choose to do so, that's another
matter, but we should not be *forcing* Theme developers to make all of their
custom Theme functions pluggable ( ! function_exists() wrappers) or
hookable.

Perhaps a better implementation here would be to find a
positive-reinforcement means to encourage child-ready Themes?

Chip

On Sat, Jan 22, 2011 at 11:04 AM, Edward Caissie
<edward.caissie at gmail.com>wrote:

> I would say if the addition to 7) is added then the addition to 6) would
> less of a requirement to insure a theme is "child-able". Although
> best-practice coding is always a good thing to recommend.
>
>
> Cais.
>
>
> On Sat, Jan 22, 2011 at 11:49 AM, Otto <otto at ottodestruct.com> wrote:
>
>> > 6) (if) a functions.php exists, it must be compatible with the latest
>> > version of the parent theme
>>
>> On this note, it might be a good idea to start suggesting that all
>> themes with functions.php files be child-able. By this, I mean that
>> everything in the functions.php should be in a hooked function or have
>> a if !defined / !function_exists wrapper around it. Some best
>> practices could be drawn up.
>>
>> > 7) (if) parent theme is updated, all child themes must be updated within
>> a
>> > reasonable amount of time to fit with the current parent if applicable ?
>>
>> That a reasonable question: How to handle breakage. Parents can make
>> radical changes that will break children. Maybe create a list of
>> themes that are "designed to be parents"? Dunno.
>
>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20110122/2a21e4bf/attachment.htm>