Opened 13 years ago
Closed 13 years ago
#4281 closed defect (fixed)
Debugging Dojo 0.9: missing dojo.hostenv.writeIncludes
Reported by: | guest | Owned by: | anonymous |
---|---|---|---|
Priority: | high | Milestone: | 1.0 |
Component: | Core | Version: | 0.9 |
Keywords: | Debugging, writeIncludes | Cc: | |
Blocked By: | Blocking: |
Description
In 0.4 there was dojo.hostenv.writeIncludes() to get all loaded modules written to a script-tag for debugging. Now I can't find it anymore. There ist just the stub dojo._writeIncludes().
How to debug Dojo 0.9 modules?
After all, the Dojo Book 0.9 isn't updated in this matter yet.
Change History (2)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
Milestone: | → 1.0 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
I updated the book page with the info I mentioned above: http://dojotoolkit.org/book/dojo-book-0-9/part-4-meta-dojo/debugging-facilities/debugging-flags
Thanks for finding the documentation problem. I'm going to close this bug as fixed, and use #3583 to track progress with a debugAtAllCosts replacement.
Note: See
TracTickets for help on using
tickets.
The old debugAtAllCosts functionality caused a lot of issues, and a lot of support questions, so we were hoping to find something that worked better, or tools that supported direct debugging of evaled code.
For instance, the in-development Fireclipse Firefox plugin. It adds support for evaled debugging to Firebug. You can get it from http://fireclipse.xucia.com.
There is an open ticket to support debugAtAllCosts in ticket #3583. It is marked for the 1.1 release, but I hope to have something for 1.0, assuming we can get agreement on the approach.
I'll see if I can update the Dojo 0.9 book to contain this info.