[TYPO3-mvc] Harmonization and Streamlining of CMS Fluid and FLOW Fluid
Bastian Waidelich
bastian at typo3.org
Tue Mar 24 12:41:25 CET 2015
On 23.03.15, at 19:47, Claus Due wrote:
Hi all,
great that this topic gets some traction again!
> [...] the smaller the Fluid core is and the fewer
> choices this template engine makes about everything framework
> specific the easier it will be to maintain *Fluid*.
>[...]
> Let us not force our decisions about MVC, forms, controllers,
> validation, messaging, security etc. onto everyone else. We can
> provide a secondary tool that does this "the TYPO3 way" but we
> so very much should not try to force others to follow this way.
For the record: I fully agree.
I could imagine a mechanism that allows for registering single
ViewHelpers to be available in the "f" namespace.
That way we could still provide a "compat" package/extension for a grace
period.
BTW: I just stumbled upon yet another effort from Google Summer Of Code
2013: https://github.com/Puja0708/GSoC-TYPO3.Base (and
https://github.com/Puja0708/GSoCNew-TYPO3.Fluid as Flow adapter).
I didn't really look into the code, but it's astonishing that we have so
many independent takes on this. Let's collaborate! ;)
--
Bastian Waidelich
More information about the TYPO3-project-typo3v4mvc
mailing list