I c. Thanks for clarifying.
Looks useful.
Again, thank you for contributing. I added your repo to my watch list
on github.
On Jan 20, 6:32 pm, nx wrote:
> Yeah, so if you had a "photos" controller and you want people to be
> able to submit photos through your Radiant site:
>
> Request -> Action
Yeah, so if you had a "photos" controller and you want people to be
able to submit photos through your Radiant site:
Request -> Action -> Radiant Page Used for Rendering
/photos -> index -> /photos
/photos/29 -> show -> /photos/show
/photos/29/edit -> edit -> /photos/edit
/photos/new -> new -> /ph
On 20.01.2011, at 23:02, nx wrote:
> share_layout, as far as I know (haven't used it), uses templates (ERB,
> Haml, whatever) rendered from the action and wraps the rendered
> template in the Radiant layout.
>
> render_radiant, on the other hand, uses a Radiant page matching the
> path of the /c
share_layout, as far as I know (haven't used it), uses templates (ERB,
Haml, whatever) rendered from the action and wraps the rendered
template in the Radiant layout.
render_radiant, on the other hand, uses a Radiant page matching the
path of the /controller/action as the "template" in this contex
On 20 Jan 2011, at 21:38, swartz wrote:
> I gave a very brief look at your extension.
> I do not mean to devalue your contribution(in fact, thank you for it),
> but isn't this what share_layout extension does?
> https://github.com/radiant/radiant-share-layouts-extension
>
> Also check spanner's f
I gave a very brief look at your extension.
I do not mean to devalue your contribution(in fact, thank you for it),
but isn't this what share_layout extension does?
https://github.com/radiant/radiant-share-layouts-extension
Also check spanner's fork:
https://github.com/spanner/radiant-share-layouts
