[TYPO3-mvc] Harmonization and Streamlining of CMS Fluid and FLOW Fluid

[Markus Klein]

> 
> Hi Markus,
> 
> Markus Klein wrote:
> 
> > The only thing is that we have to find a backwards compatible solution
> > to mix the Fluid-shipped VHs with the product-shipped VHs in the same
> > namespace (f), otherwise we'll get a breaking change.
> 
> I already said more than a year ago, that product-shipped VHs need to be
> moved to their corresponding package.
> E.g. in CMS the cObject viewhelper should be part of frontend and not fluid,
> f:be.* should be in backend, etc.
> 
> Then we would not have this problem now.
Well, yes and no. What about the f:link.action viewhelper? You need it in BE and FE, so why duplicate it?
I'd rather do the separation in terms of "what applies where". Link-VHs are product-specific, but yet FE/BE independent. Control-Structures (for, if, switch) are product-independent and are more like a "language feature", hence it should be part of Fluid itself.

> 
> Best regards
> --
> Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln Documentation
> – Active contributor TYPO3 CMS
> TYPO3 .... inspiring people to share!
> 


Kind regards
Markus

------------------------------------------------------------
Markus Klein
TYPO3 CMS Active Contributors Team Member