debug=true and loading things in dojo.require
We noticed some of our code that does not work due to "Could not locate widget implementation for XXXX in dojo.widget registered to namespace dojo" starts to work when we use debug=true in the URI.
Code that has the above issue uses dojo.require() for all the widgets it needs. For some cases, if I move dojo.require for the missing widget into code that is loaded earlier (e.g. Workbench.js), the code starts to work without debug=true.
Any ideas?
Code that has the above issue uses dojo.require() for all the widgets it needs. For some cases, if I move dojo.require for the missing widget into code that is loaded earlier (e.g. Workbench.js), the code starts to work without debug=true.
Any ideas?
12 answers
John Barton at IBM Almaden has been working on a patch for Firebug so it can debug code in evals. You can find the experimental code at http://fireclipse.xucia.com/ FWIW, other debuggers like MSVC and Drosera can already handle this, to some extent, so another answer is to try it in IE.
All that said, I still find that debuggers, particularly Firebug, tend to miss exceptions from time to time.
All that said, I still find that debuggers, particularly Firebug, tend to miss exceptions from time to time.
Adam,
Thanks for the headsup on this. Definitely has some great new features.
A word of warning to anyone who tries this though. I would suggest
disabling firebug for jazz.net as I have found that it makes the browser
unresponsive for quite some time.
Richard
apeller wrote:
Thanks for the headsup on this. Definitely has some great new features.
A word of warning to anyone who tries this though. I would suggest
disabling firebug for jazz.net as I have found that it makes the browser
unresponsive for quite some time.
Richard
apeller wrote:
John Barton at IBM Almaden has been working on a patch for Firebug so
it can debug code in evals. You can find the experimental code at
http://fireclipse.xucia.com/ FWIW, other debuggers like MSVC and
Drosera can already handle this, to some extent, so another answer is
to try it in IE.
All that said, I still find that debuggers, particularly Firebug, tend
to miss exceptions from time to time.
page 2of 1 pagesof 2 pages