[TYPO3-core] RFC: 10964: ExtJs prototype-adapter leads to several IE-errors

Dmitry Dulepov dmitry.dulepov at gmail.com
Wed Apr 22 23:20:55 CEST 2009


Hi!

Dmitry Dulepov wrote:
> -1. There is no need to force this on people. Give them the choice :)
> Keep the adapter because some people may need it. If you remove it,
> people will have to install an alternative copy somewhere. Shipping
> ExtJS with core allows people to rely on it. If you limit the copy,
> you limit the relation. There is no advantage.
> 
> It does not hurt to have this file. Just do not use it for core.

May be a use case will help to understand it better.

I had a project where I had to use effects. ExtJS does not provide enough of them, so I used Scriptaculous. Scriptaculous needs Prototype. To minimize the whole stuff I used the Prototype adapter, which worked very well for that project. Changing it to Ext adapter would only increase JS download size but will not provide any advantages. So the optimal choice for certain projects will be the Prototype adapter.

-- 
Dmitry Dulepov
In TYPO3 blog: http://dmitry-dulepov.com/article/have-fun-with-the-typoscript-error-hunt.html
LinkedIn: http://www.linkedin.com/in/dmitrydulepov
Twitter: http://twitter.com/dmitryd
Skype: liels_bugs


More information about the TYPO3-team-core mailing list