Add possibility of rte dynamic css

[kaystrobach]

needs some thougths -> options define name in ts -> link in page module, needs to respect templates as well -> relativ complex :D

[kaystrobach]

@Laslow any idea how to solve this? basicly we would need to have a dynamic name, which is consistent between FE and BE and we would also need to know all the TS variables from the frontend.

[Shade634]

i kinda miss the issue here, you can take over the same generated file for the rte content for front-end and backend?

[kaystrobach]

the idea was to include the dynamically generated css file here.

for themes it should be enough to include a once generated css file, atleast for the first version ...

[Shade634]

yea, the only hard thing in here is the #content divs and classed styled content, other then that, the default style can be simply implemented by implementing the all.css

[kaystrobach]

that is the nice thing about less and sass: you can do sth. like:

--------------------
rte.less
--------------------
.bla {
}

--------------------
content.less
--------------------
#content {
 @import rte.less; 
}

the resulting css will have sth. like:

#content .bla {
}

and then you can include content.less in the frontend and the rte.less in the backend, but the dynamic TS overlay makes it more complex ;)

[kaystrobach]

architectural we need to do:

• parse sys_template to get overrides
• parse and modify pageTS similar to fe (less file gets replaced with resulting css)

[kaystrobach]

just checked out some stuff here.

the function \TYPO3\CMS\Rtehtmlarea\RteHtmlAreaBase::getContentCssFileName has no way to replace that file.

So an easy solution would be to provide that file as css e.g. in the pageTS with a theme.
another option would be to directly hook into the pagets rendering and exchange the css ... but this is rather ugly imho.

I would prefer to close this for now, until we have a fast and reliable solution, as we would normally need to parse the constants from the sys template record and pass them to the renderer

[mkoitka]

For completeness' sake, the RTE method for registering the CSS has changed in TYPO3 7.x.

See current TYPO3 API

Apart from that it's quite an appreciated feature. How do you guys currently handle it? Any workarounds?

I don't know how important the TS overlay is, perhaps it's acceptable to first go without it for the RTE, if documented properly. ;)

[kaystrobach]

i think i will check this again once we have the new RTE 😄 in TYPO3 CMS 8