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

[Philipp Gampe]

Hi Claus and Markus,

Claus Due wrote:

> I did take a look and here is a short list of framework-specific
> components on which the `f:form` scope depends:

And therefore should be part of the package that provides the logic to the 
viewhelpers, thus whatever Flow package this is, in CMS this would be the 
extbase package (extension). The viewhelpers are useless without extbase and 
thus should be part of extbase and not part of the template engine.

In the special case of extbase, it might make sense to decouple even more 
and put them into a dedicated form package, because extbase does to much in 
one package (DI, Models, Controllers, Repositories, Mapping, Request 
Handling).

So yes, please go ahead and move all viewhelpers that cannot be used with a 
standalone fluid.

As a rule of thumb, I would say that a viewhelper should be ship the the 
package that is required by the viewhelper.

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