Jan 15, 2009, 11:18 AM
jQuery 1.3 and Ext adapter with Coolite
Hi,
I am new to Ext JS and Coolite, but have been using jQuery for a while.
We are looking into ExtJS/Coolite right now, but we'd like to keep our investment in jQuery. The jQuery adapter support is appealing. But looking at Coolite 0.7, the latest jQuery is 1.2.3.
jQuery 1.3 is out and we'd like to use that. I am investigating options and best practices.
For example, I can include jQuery 1.3 manually in the head of the html. Because jQuery detects if there is already an instance running, if Ext were to try and load 1.2.3 via the adapter mechanism, it won't load it, but jQuery 1.3 will still be available as the adapter for Ext. A few quick test pages using Coolite 0.7 and jQuery 1.3 in this way seems to work quite nicely (on a limited number of tests using a view layouts, toolbars, panels, etc).
But is this recommended?
The alternative is I keep the Ext adapter as default, and load jQuery 1.3 anyway for our other bits.
The extra hit of dowloading another framework is probably something we can accept as our app is for intranets, but avoiding that would be nice, if possible?
Thanks!
I am new to Ext JS and Coolite, but have been using jQuery for a while.
We are looking into ExtJS/Coolite right now, but we'd like to keep our investment in jQuery. The jQuery adapter support is appealing. But looking at Coolite 0.7, the latest jQuery is 1.2.3.
jQuery 1.3 is out and we'd like to use that. I am investigating options and best practices.
For example, I can include jQuery 1.3 manually in the head of the html. Because jQuery detects if there is already an instance running, if Ext were to try and load 1.2.3 via the adapter mechanism, it won't load it, but jQuery 1.3 will still be available as the adapter for Ext. A few quick test pages using Coolite 0.7 and jQuery 1.3 in this way seems to work quite nicely (on a limited number of tests using a view layouts, toolbars, panels, etc).
But is this recommended?
The alternative is I keep the Ext adapter as default, and load jQuery 1.3 anyway for our other bits.
The extra hit of dowloading another framework is probably something we can accept as our app is for intranets, but avoiding that would be nice, if possible?
Thanks!
