[TYPO3-dev] FluidPage Extension

[Zachary Davis]

Søren,

We'll definitely work with you. I'm all for having _one_ extension that 
provides this functionality and provides it well. I don't care if that's 
our extension, your extension, or somebody else's. I'm tied up this week 
at a conference, but when I get back to the office I plan on installing 
your ext and taking a look at it. Once I've had a chance to check it 
out, I'm all for scheduling a meeting and continuing the discussion.

best,
Zach



Søren Malling wrote:
> Hi Zach,
>
> Thanks for mentioning my article!
>
> To everybody :
>
> I'm not trying to reinvent the wheel or doing a ripoff!
>
> fluidlayout has been working progress since august, but extension and
> article wasn't released untill this week due to lack of time.
>
> I would love to see fluidpage, basictemplate and fluidlayout bundle
> together as a great FLUIDTEMPLATE + backend_layout tool with great
> features and functionality!
>
> If you don't mind, please add you feature requests etc. in the forge
> project of fluidlayout (or basictemplate) so we can keep track of
> requests and bugs!
>
> http://forge.typo3.org/projects/extension-fluidlayout
>
> http://forge.typo3.org/projects/extension-fluidlayout/issues/new
>
> And I will like to ask Zach and the rest of the Cast Iron Coding team
> and Kay S to join forces together with me?
>
> Currently only fluidlayout got a manual (well, a blog post, no .sxw
> document), but could we start by creating a short video cast showing the
> functionality (installation, setup, outcome) of each extension?
>
> And let's meet on the Big Blue Button and talk about our plans for these
> extensions?
>
> Regards,
>
> Søren
>
> On 24/10/11 18.00, Zachary Davis wrote:
>> In case you missed it, check out Soren's extension:
>>
>> http://buzz.typo3.org/people/soeren-malling/article/fluidtemplate-selector-and-backend-layout/
>>
>>
>>
>> I haven't looked at it in much detail yet, but it appears to be similar
>> to what we're doing.
>>
>> IMHO, 4.7 should really strive to cleanly tie together backend layouts
>> and fluid templates as the de facto method for creating page templates.
>> 95% of the underlying functionality is already present in TYPO3 and it
>> would be great if extensions like ours weren't even necessary.
>>
>> Zach
>>
>>
>>
>> Kay Strobach wrote:
>>> Hi,
>>>
>>> there is something similar:
>>>
>>> EXT:basictemplate (Done with FLUIDTEMPLATE also).
>>>
>>> Grüße
>>> Kay
>>>
>>> Am 21.10.2011 01:28, schrieb 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
>>>
>>>
>