[TYPO3-english] How to be sure ExtJS is well-loaded in my FE?
Steffen Kamper
info at sk-typo3.de
Mon Mar 21 10:39:30 CET 2011
Hi,
Am 21.03.2011 09:44, schrieb Bjoern Pedersen:
> Am 21.03.2011 09:39, schrieb Steffen Kamper:
>> Hi,
>>
>> Am 21.03.2011 09:22, schrieb Bjoern Pedersen:
>>> Am 21.03.2011 09:01, schrieb François Suter:
>>>> Hi,
>>>>
>>>>> don't use ExtCore and ExtJs parallel. ExtCore is a "small" compilation
>>>>> of ExtJS just for some little widgets and effects.
>>>>
>>>> That was it! Thanks a lot.
>>>>
>>>> I guess it's not obvious for people who don't know ExtJS very well that
>>>> both libraries should not be loaded. I have added an issue to the TSref
>>>> tracker to make the description more explicit:
>>>>
>>>> http://forge.typo3.org/issues/13936
>>>>
>>>> Cheers
>>>>
>>> Wouldn't it be even better if page.javascriptLibs checks wether ExtJS
>>> is set and then automagically only loads the full library? Otherwise it
>>> will lead to hard to detect problems if the loading is triggered from
>>> some extension TS. I will file a bug and patch.
>>>
>>
>> i don't think so. Normally you know what to use: ExtCore or ExtJs. Core
>> doesn't need to check conflicting js libs, there are several
>> possibilities to load conflicting stuff.
>>
>> vg Steffen
>
> Well just imagine this situation:
> In your top level TS you load ExtCore
> (page.includeLibraries.ExtCore=1). In some sub-page extension template
> you include an extension template that loads ExtJS
> (page.includeLibraries.ExtJS=1) .
> You will have difficluties to find the problem.
>
> The check will of course only be effective if you use the TypoScript
> shortcuts:
> page.includeLibraries.ExtCore
> and
> page.includeLibraries.ExtJS
>
> It will not generally check for conflicting libs.
>
ok, please file a bug. We can exclude ExtCore if ExtJS is included.
vg Steffen
More information about the TYPO3-english
mailing list