[wp-hackers] Grandchild themes

[Nathan Rice]

FWIW, a "framework" is a "framework" whether it's a parent theme that
doesn't get modified, a drop-in folder within a standalone theme (which
doesn't get modified), or even in a plugin, really. In reality, WordPress
itself is a "theme framework", but it exists in a separate layer than the
currently active theme. Trying to define an object as a methodology seems
dumb to me.

------------------
Nathan Rice
WordPress and Web Development
www.nathanrice.net | twitter.com/nathanrice


On Wed, Jun 8, 2011 at 10:42 AM, Doug Stewart <zamoose at gmail.com> wrote:

> On Wed, Jun 8, 2011 at 9:52 AM, Chip Bennett <chip at chipbennett.net> wrote:
> > This may sound overly pedantic (I am, after all, a self-avowed pedant),
> but
> > I would use the term "Stand Alone Theme" rather than "Parent Theme" in
> this
> > context. Technically *Any* fully functional (i.e. "Stand Alone") Theme
> can
> > act as a "Parent", but a Stand Alone Theme only becomes a "Parent" Theme
> if
> > some other Theme claims it as its template.
> >
>
> Not entirely true. Some themes are Not Safe For Parent Use (NSFPU),
> particularly those that willy-nilly mix TEMPLATEPATH and
> STYLESHEETPATH.
>
> --
> -Doug
> @zamoose
> http://literalbarrage.org/blog/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>