[TYPO3-team-core-v5] Fluid CSSEngine folder structure question

[Bastian Waidelich]

Sebastian Kurfürst wrote:

> this list is perfectly OK as well I think :-)

Well, actually it should be used for release planning IIRC. But given 
the low traffic I don't think it's too bad ;)


>>> \Packages\Framework\Fluid\Classes\CSSEngine\CSSEngine.php
>>> \Packages\Framework\Fluid\Classes\CSSEngine\Plugins\

> I'm not yet sure about the "Plugins" folder, as it would be nice to be 
> able to define plugins in custom packages and "inject" them there.
> But we can work out how this detail can work lateron :-)

I think, a "Plugin" folder is fine. Later you should be able to define 
additional plugin folders through the settings.


> Maybe the naming is better like CssEngine?

+1


> we use "UriBuilder" etc as well and others

we don't actually.. But I'm about to rework the URIBuilder for FLOW3 & 
Extbase and with the patch I'll suggest a renaming too.


> Does it make sense to have the CSS Engine as a standalone package, or 
> rather integrated into Fluid? Hmm...

My opinion is: When a package can make sense without the other, create 
two packages.


> Integrated into Fluid seems to make sense so that the ViewHelper can be 
> in the "f"-Namespace, too.

That's right, but we'll have that problem sooner or later.
I think, it would be great to be able to specify Fluid namespaces 
globally in the settings, so you don't always have to specify them in 
the templates.


> Looking really forward to your work :-)

me too, keep up!

Bastian