#10032 closed bug (invalid)
$.getScript fails to load ext.js framework
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | 1.6.3 |
Component: | misc | Version: | 1.6.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Ladies & Gentlemen,
For some reason (I haven´t quite figured out why) if I load the ext.js framework with $.getScript as well as require.js, it fails to function (the framework itself contains a js loader and is probaply not designed to be loaded asynchronously).
However, when I use JSL it does work.
Attached the coffee-script loading part of my app:
# Ext.Js framework works perfectly :) jsl.load "/js/ext/ext-all-debug.js", ->
jsl.load "/js/extensible/extensible-all.js", ->
currentView.calendarview('load')
# Ext.Js framework doesn´t work :( $.getScript "/js/ext/ext-all-debug.js", ->
$.getScript "/js/extensible/extensible-all.js", ->
currentView.calendarview('load')
I use it as part of a jQuery widget that on create should load the Ext.JS Framwork. I could not figure out why that was, one thing I could figure out is that Ext.onReady fails to fire when loaded via $.getScript.
I hope that information helps. I´m sorry to not have figured out why it doesn´t work.
Regards, Thomas
Change History (4)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Sorry for that. I´ve narrowed it down, pure ext.js works nicely.
The combination of then using the ext.js loader to load http://ext.ensible.com/products/calendar/ doesn´t. I´m still trying to get it into jsfiddle, but the loader part of ext is hard to get to work there, which might be due to the fact that loading modules from another domain causes problems.
comment:3 Changed 11 years ago by
Component: | unfiled → misc |
---|---|
Milestone: | None → 1.6.3 |
Priority: | undecided → low |
Resolution: | → invalid |
Status: | new → closed |
It's not jQuery's responsibility to ensure that Ext.js fires it's ready handlers
comment:4 Changed 11 years ago by
Ok, please close the bug. I can´t make the code work in jsfiddle due to Access-Control-Allow-Origin errors.
I´ll simply leave it at that and use JSL :)
Sorry for not providing a jsfiddle.net example... It seems to have it´s own issues with ext.js... :o