[TYPO3-project-4-3] CSS BE issues

[Uschi Renziehausen]

Hi Francois and *

i do agree with you about the necessity of naming conventions, but in the end to have to start somewhere with our 
cleanup and I think, Steffen went the right way when chosing the suggested names: Q: What do we need to style? A: 
Modules with docheaders and those without? mod-with-docheader and mod-no-docheader reflect that.

Apart from that here some suggestions for general rules for classnames.

1) No capital letters. To improve readability, we use a dash (-).

2) Classnames should be as short as possible, means, let us get rid of meaningless prefixes like typo3- or let us at 
least shorten them to t3-...

3) Classnames should not reflect the markup. Currently we have stuff like wrapperTable, wrapperTable1 and so on. What 
happens if the markup changes and we get rid of those tables?

4) Let us use the same classes for the same purpose throughout the whole BE. If we want alternating colors the 
presumably we want the same colors for every list. Currently we have sort of a mess here:
- In module Web>List we use db_list_normal for odd rows and db_list_alternate for even rows
- In module File>Filelist we use bgColor6 for odd rows and bgColor4 for even rows (same in Admin tools > User Admin, 
where you can only see alternating colors if you really compare some things and the classes are applied to td instead of tr)

Imho we should have two (or perhaps like in extjs.css only one class) for alternating blocks/rows, somehow like this:
- t3-odd vs. t3-even or
- t3-section-even vs. t3-section-odd or
- t3-section-normal vs. t3-section-alt


Uschi


Francois Suter schrieb:
> Hi,
> 
>> for the long term (4.4) mainly yes, for the short term (4.3) not.
>> Imho it's enough to add 2 classes to body of modules:
>> .mod-with-docheader
>> .mod-no-docheader
>> and assign basic rules for this and the childs.
> 
> I think it's too early to decide on names. We should really decide on 
> naming conventions first.
> 
> Cheers
>