[TYPO3-dev] FluidPage Extension

[Zachary Davis]

For one, it ties the backend layout to the template that's rendered on 
the frontend. Without an extension, there's not a good way (that I know 
of) to figure out what template to use on a page, since you need to walk 
up the rootline and determine if the template is inherited from a parent 
page or from the current page.

I suppose you could use a fluidtemplate object, although I prefer not to 
have to setup that object for every template choice. This way, there are 
some conventions around how variables are assigned to the template, 
which speeds up our process a bit (eg, the page is accessible as {page} 
within the view, the ID of the backend layout is assigned, etc.

All that said, it's TYPO3 so of course there are many (probably too 
many) ways to do the same thing ;)

Zach


Philipp Gampe wrote:
> Zach Davis wrote:
>
>> We released our fluidpage extension on github today after receiving some
>> requests to make it public (see this blog post for some backstory:
>> http://castironcoding.com/resources/our-blog/sp/view/single/post/reason-9-
> for-choosing-typo3-fluid-templating-engine.html).
>
> Even after reading your article and the comments,
>
> what are the real benefits over the FLUIDTEMPLATE cObject?
>
> You did some changes to TCA and TSconfig, what else does it provide which is
> not possible with a plain TYPO3 (4.5)?
>
> Best regards