public
Description: An extension for Radiant CMS that allows controllers to render their views within Radiant layouts.
Homepage:
Clone URL: git://github.com/radiant/radiant-share-layouts-extension.git
mariozig (author)
Tue Jun 16 18:02:55 -0700 2009
seancribbs (committer)
Thu Jun 18 08:47:57 -0700 2009
commit  c3c94aa98e337df38f6ac7630ba7659923439cce
tree    5f1ee146ab708e00f965c31cbd9f94e53271c217
parent  41997f18a5ce640412150e934ebfd6934845c60b
name age message
file README Fri May 22 06:52:17 -0700 2009 Updated README [jfahrenkrug]
file Rakefile Tue Jun 24 08:24:21 -0700 2008 Allow RailsPages in the tree to provide content... [seancribbs]
directory app/ Loading commit data...
directory lib/ Mon Nov 17 19:34:50 -0800 2008 Fixed bug with breadcrumbs, added/improved supp... [chrisparrish]
file share_layouts_extension.rb Thu Jun 18 08:47:57 -0700 2009 Change URL to point @ the Github based wiki. P... [mariozig]
directory spec/ Fri May 22 06:49:24 -0700 2009 converted all the tests to specs [jfahrenkrug]
README
= Share Layouts

Created by: Sean Cribbs (seancribbs AT gmail DOT com), September 20, 2007
Updated to work with 0.8 RC1 by: Johannes Fahrenkrug (http://springenwerk.com), May 22, 2009

Allows Rails controllers/actions to use Radiant layouts as their "layout".  
content_for blocks are mapped to page parts, with the exception of :title and
:breadcrumbs, which map to their specific default tags. The default content, 
or @content_for_layout, is mapped to the 'body' part.

== What to do in your controllers

  radiant_layout 'Layout name'

-or-

  radiant_layout { |controller| # some code to determine layout name }

radiant_layout takes the same options as the built-in layout.  To specifically
override the Radiant layout and use a standard Rails one use 
:layout => "mine", or :layout => false for no layout, as options to render.

To choose a different Radiant layout, set the @radiant_layout instance 
variable to the name of a Radiant layout in your controller or view.

== Acknowledgments

Thanks to John Long for clarifying and simplifying the process for me!
Thanks to xtoddx for improving the tests and support for tags that use the 
request and response.
Thanks to Digital Pulp, Inc. for funding the initial development of this
extension as part of the Redken.com project.