[TYPO3-content-rendering] More accessible forms: tt_content.search.30 / tt_content.login.20 in TYPO3 4.0rc1

[Elmar Hinz]

Franz Koch schrieb:
> Don't treat this personally, but WHY do you guys always use classes like
> "csc-rendertypewhatever-xyz" for class-names inside a 'container class'?
> Why no simple "form-xyz", "form-radio", "form-submit"? If a webmaster
> wants to style f.e. the searchform different from any other form inside
> typo3, he can use "div.csc-searchform .form-field" to address this
> specific element. But as a great plus a general and cross-extension
> styling for elements (f.e. "form-radio") or whatever would at least be
> possible with minimum ammount of css-code and could be a first aproach
> in the direction of typo3-rendering schemes.
> 

That is a good point. The classnames in TYPO3 are often are
"informational overloaded" wich also blows up the code. On the other
hand it is to discuss if the named container DIV are allways desired.

See: RFC: default wrap for each CE? (section_frame) from 19 Jan 06.

I wrote her on 20 jan 06:

<quote>
I wouldn't set it as default.

If we put Peters proposal into a "classy" extension, one can install
that setting as a possibility. It could match with the idea of Contend
Rendering Schemes. Thorsten has already initiated a page to collect
proposals for this:

http://wiki.typo3.org/index.php/Content_Rendering_Schemes

I think we maybe need 2 or 3 scheme extensions. One that produces a
very clean sourcecode in the sense of Ben. The other one that offers
more divs and classes for a lot of frames and other styling possibilities.

<quote>

I would appriciate it when the discussion would make some progress and
come to some results.

Regs

Elmar