On Tue, Oct 28, 2008 at 3:46 PM, Adam van den Hoven <
[EMAIL PROTECTED]> wrote:
>
> The benefit is being able to sparsely populate data. Where the content
> author is the person doing the technical admin, its not an issue. but if you
> have many non-technical authors (a good reason for using a CMS) then
> sparsely (only where you want things to change) is very beneficial.
>
I agree that sparsely populating data is a benefit of the inheritance of
page parts (and other things which may be inherited). But the current method
of specifying inherit="true" in the Radius tag enjoys this benefit, and
making inheritance the default (so that local="true" is used for Radius tags
which should not be inherited) doesn't add anything.
Your example of the widgets image (a "page variable") being set for
/products/widgets and being inherited by /products/widgets/legal/privacy,
and then setting that same page variable to a pirate image just for
/products/widgets/legal, I think is made moot by the paperclipped and
page_attachments extensions. I'm having a hard time thinking of any other
use case where your suggestion would be easier than just <r:var name="foo"
inherit="true" />. Page attributes like created_at, updated_at, title,
meta_description, meta_keywords, etc., all seem like things that should *not
* be inherited by default.
Perhaps you're just pointing out the ideal behavior already present in
extensions like the mailer extension, that makes available
extension-specific tags available which make sense to be inherited by
default. In one Radiant site, I've placed all of the configuration necessary
for a mailer form on the Home page (page parts mailer, email_plain,
email_html). Then I have the following:
email_form snippet:
<r:mailer:form name="contact"> … </r:mailer:form>
sidebar page part of Home page:
<r:snippet name="email_form" />
In my layout:
<r:content part="sidebar" inherit="true" />
The mailer extension automatically inherits the configuration page parts to
the rendering page, and everything works nicely.
I think this behavior is extremely useful on a per-extension basis, but I'm
not sure it has a place in core.
--
Tim
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
