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

[Claus Due]

> Obviously I didn't make myself clear enough: That's exactly my point!

> Still I'd somehow try to keep the viewhelpers like f:form.
> I didn't look too much into the code there and how much dependencies
> on the product is in there, but if we manage to keep those central, I'd
> would be beneficial.

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

* Request
* Request validation/validation-result
* Controller context
* Controller argument mapping awareness (might be removable)
* Link generation
* Hash protection
* Domain specific naming
* Flashmessage concept
* Error/Message objects

And those are just the immediate dependencies. IMHO that list means it
shouldn't even be attempted to create a package that works standalone...

> I'd go an integrate those product-specific VHs deep into the product.
> Hence not even a separate package, but ship them with CMS Core for
> instance. (either in the sysext Core/Frontend/Backend, wherever they fit best)

Sure, no objection from me on that point. I was only speaking about one
possible way to *access* and *migrate* those framework-specfic helpers.
Where they reside is irrelevant (at least to me), as long as it is outside Fluid.