[TYPO3-dev] CSC and ContentRendering Team

[Steffen Ritter]

Denyer Ec schrieb:
> many 3rd party extensions rely on the CSC markup structure for correct
> operation. I'd hope none *depend* on it, but my instincts say
> otherwise.


Many do... Look at all lightbox stuff, ringer extensions, frame 
extensions etc. they are based on changing ts code of csc.
What ab out "download" extensions changing csc download rendering...

So I think, if we might have a new "version" of CR, with is optional 
forever, nobody will use ist since, the most other "fine effects" won't 
work with it until the extensions do only support the new stuff. And the 
   extensions won't be changed if there's no real need to...


So we are in a kind of vicious circle. We have to break up at one point, 
if we have to run out.

But shure you are right. We should develope a roadmap how to proceed.

I would add before you're first step:

  - analyze current situation. There are many thinks which aren't used 
in csc anymore (coming from the old CR) or things/db fields which are 
"misused" som kind of... Some option might not be very useful oder 
others might even not be used.

  - based on this we should look how all the variants of our CSC should 
be rendered ideally. example (HTML-Templates)

- We also should provide a css set using as less classes as possible - 
but meaningful names.

- Based on this we might start restructuring TS and CSC Class, what - as 
you already pointed out - would be the lightest part.

But before starting working on such a thing, assigning tasks and 
timeframes, we should have a straight "implementation guideline" in 
discussion with core-team, that all (ext-devs, core-devs, admins etc) 
can prepare what step has to be done when, in which version etc...

I would really look forward to see any progress here..

Steffen