[TYPO3-mvc] Fluid: Fallback paths for templates

[bernd wilke]

Am 19.07.13 02:14, schrieb Claus Due:
> Hi Bastian,
>
> Thanks for the reply.
>
> You write:
>
>> ....it's not easy to tell what path is being looked up first (in this
>> case it's EXT:bar/Resources/Private/Templates/ I guess)
>
> Yes, such is the nature of an atomic configuration as combined with the
> nature
> of programming languages. Thankfully, "we's ain't stupid, y'all".
>
>> and the configuration might be spread around multiple extensions & TS
>> templates.
>
> Yes. That is the whole point. It's the entire reason for this feature.
>
> You're thinking of all this as "one site, one package contains full
> configuration"
> when you should be seeing it as "one site, many packages contain config,
> one
> package contains supplemental config, fill-in-gaps style".
>
> You view the atomic nature of this configuration as a problem. I view it
> as a key
> selling point. You think of how to debug sites easier, I think of how to
> make their
> creation and modification easier. No surprise that we don't agree on
> this ;)

I like the advantages of a spread, selective replacement of single 
templates.
but also know the confusion of different replacements of single files as 
you search for the currently active template-file, which can be one of 
multiple.

for debugging purposes an overview might be needed where you can see a 
list of all active/currently accessible templates.

another nice feature might be the copy/export of all the active 
templates to one path. easier to debug, simpler to export as a theme to 
another installation.

bernd
-- 
http://www.pi-phi.de/cheatsheet.html