- @OneFineJay @LisaSabinWilson @jschuller & Child-Theme concept is currently being abused, but I guess we're not ready to cross that bridge in reply to OneFineJay #
- @OneFineJay Child Themes are intended for the user to make update-proof Theme changes, but are instead being used as premium-Theme skins in reply to OneFineJay #
- @OneFineJay I guess I'm sold on @iandstewart's view re: framework/Theme/child-Theme. But if users are happy, what do I care, really? in reply to OneFineJay #
- @andreasnrb I agree, but the feature was rolled out without any real guidelines regarding intended use/best practice. in reply to andreasnrb #
- @LovinBlue @pwilson24 like they can stop him even if they game-plan for him... that pass defense is... not good. in reply to LovinBlue #
- @andreasnrb agreed, but it also sets a bad precedent for others to implement. I thought about, but decided against, doing that for Oenology in reply to andreasnrb #
- @OneFineJay yeah, http://is.gd/iRhxD is the one. I meant @justintadlock, not @iandstewart (though I'd wager his views are at least similar) in reply to OneFineJay #
- @andreasnrb how so? Tthere are certainly valid uses for Child Themes. in reply to andreasnrb #
- @andreasnrb then a previously-met need has been reintroduced, as it now is unmet by Child Themes. Will we eventually see grandchild Themes? in reply to andreasnrb #
- @OneFineJay have you taken a look at Oenology? http://wordpress.org/extend/themes/oenology <- all feedback/comments/criticism welcome! in reply to OneFineJay #
- @flashingcursor there's definitely an opportunity for education there. I see no problem with devs adding Theme-specific functions to Themes in reply to flashingcursor #
- @coltsgirl17 it's a hoax. in reply to coltsgirl17 #
