[TYPO3-dev] Developing Standards - CSS

David Bruchmann typo3-dev at bruchmann-web.de
Wed Feb 10 14:57:06 CET 2010


----- Ursprüngliche Nachricht -----
Von:        Nikolas Hagelstein <lists at shr-now.de>
Gesendet:   Mittwoch, 10. Februar 2010 14:09:13
An:         'List for Core-/Extension development' 
<typo3-dev at lists.typo3.org>
CC:
Betreff:    Re: [TYPO3-dev] Developing Standards - CSS
> Hi,
>
> Der Ringer schorch schrieb:
>> at least it would be nice to have a kind of CGL for HTML&  CSS. There
>> would be always the same classes for a list view, images and so on.
> +1
>
> It makes sense to specify the  same for JS and JS integration.
>
> Cheers,
> Nikolas


Hi,

in my opinion it is (or can be) nearly the same:

using JS-Frameworks often special HTML- and CSS-structures are required. 
As CSS-Styled-Content has predefined containers for most cases all these 
cases have to be overriden or new defined for JS-Tabpanels, 
JS-accordions, etc.
Changing Styles or Themes in those frameworks makes a lot of work 
especially when there is the intention to use them for all cases and 
perhaps also with options in RTE.
Having written an own extension for those containers I know that the 
HTML-Construction looks completley different to the standard-HTML and 
that empty containers for DHTML have to be noted inline somewhere 
(instead of at the end of the page) without changing the normal 
macrostructure of the document.
Purpose of the framework should be to find predefined structures that 
can be used for JS-Elements - perhaps without special extensions.
Afterwards skins can be designed, but first of all one or more 
base-skins have to be included (Example: ExtJS has a default blue skin 
and a gray one).

Best Regards
David




More information about the TYPO3-dev mailing list