[TYPO3-mvc] !!! FYI: Committed big refactoring of Fluid; v4 and v5 are now in sync again

[Sebastian Kurfürst]

Hey,


> Acutally I don't think it's a issue of the backporter, but more a
> general issue of FLUID and it's more or less tight integration into
> FLOW3/v4. What I would expect from a templating framework, is that I can
> easily integrate it in my project, be it a custom CMS, some small PHP
> app or whatever. So in my eyes, there should be something like a
> framework-interface that has to provide certain methods FLUID depends on
Yeah, I think as well that this would make sense, but it is just not
done yet.

Generally, I think Fluid is already "quite stand-alone", so I'd guess it
would take me about a day to set it up in a standalone project.
Initially, it had no references to the FLOW3 AOP proxy (and that's
something which is ugly, there should be rather an API method
"getClassName($object)" which handles this AOP magic internally) or
other internal in FLOW3, and I strive to this cleanness again.

But of course after that the real work starts, ViewHelpers have to be
written, etc etc.

Greets,
Sebastian