[TYPO3-ect] Ext-JS 1.0.1
Steffen Kamper
steffen at sk-typo3.de
Mon Aug 13 18:45:28 CEST 2007
Hi Joerg,
the main thing is the general CSS declaration found in ext-all.css. The
themes are only "special" formatting.
Doing special formatting is no problem by setting this in own css, but the
general (i only speak about the first line of ext-all) can destroy a given
css.
So i don't know how to do it best - changing the ext-all.css to
ext-all.css.php and conditioning the first line or lets configure the path
to the css-folder to allow a copy of the files where they can be
manipulated - may be second option is the most easy one.
vg Steffen
"Joerg Schoppet" <joerg at schoppet.de> schrieb im Newsbeitrag
news:mailman.1.1187006859.15482.typo3-team-extension-coordination at lists.netfielders.de...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Steffen Kamper wrote:
>> Hi Joerg,
>>
>> i have one general problem with including extjs from extension, the css.
>> Because ext-all.css is included all the time and inside are general
>> formats
>> for body/h/table/ul etc. it conflicts with the css of the site. So i had
>> to
>> edit this file and removed the first line.
>> To prevent this the path of this css-file has to be configurable to make
>> own
>> changes.
>>
>> vg Steffen
>>
> Hi Steffen,
>
> if the path of ext-all.css should be configurable, then someone can
> mentions, that the path to the css of the individual resources ('aero',
> 'default', 'gray', 'vista') should also be configurable?!?
>
> What do you think about this?
>
> Regards
> Joerg
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGwEmLq5Me6rRDqPURAocaAJ41NLC0jfjNBIHgM/zCh4CvCPnsUACglnfP
> xwdAtwQtNBCWm4tniwCh8/M=
> =bHwP
> -----END PGP SIGNATURE-----
More information about the TYPO3-team-extension-coordination
mailing list