On 14/1/2010 12:38 AM, Peter Degen-Portnoy wrote:
> There are two challenges we faced:
> 1. There is at least one page where we do not want to display at least one
> of the snippets called for in the most-used inner layout
> 2. There are some page parts ‹ different for each page ‹ that should appear
> in a right gutter, wherein the rest are laid out in the left div.
>
> To solve Challenge 1, we thought of two schemes by which we can suppress the
> display of the targeted snippet:
> 1. Add a part called ³No_<SNIPPET>² to the page where the targeted snippet
> should NOT be displayed
> 2. Extend the snippet tag to have a new attribute ³suppressable² so that a
> snippet that is flagged as ³suppressable =>  true² has a check box generated
> &  displayed on the /admin/page/x/edit view when the layout with that snippet
> is selected.  We can serialize the set of check boxes to support future
> expandability.
>
> To solve Challenge 2, we also came up with two solutions:
> 1. Precede the name of a page part with ³RG_² to indicate it should be
> displayed in the Right Gutter
> 2. Add a checkbox to the page part (after the reference links) ³Display in
> Right Gutter² that would use similar display rules as described above.
>    

Peter, welcome to Radiant!

I may be missing something obvious here... but for #2, it seems that 
what I would do is have 2 page parts.. one called 
"content_for_right_gutter" (obviously something less verbose) and 
another called "content_for_other_cases" and just populate whichever one 
should be put in. Or did I miss something obvious?

I don't fully understand Challenge #1 - is it that:
* there are some pages on which some snippet should not show

I wonder if it would be easiest to have another layout for pages on 
which the snippet should not show?

Cheers,
Mohit.
14/1/2010 | 1:00 AM.


_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to