To test drive it, you'll need the latest dev channel version of Chrome,
and turn on "Enable source maps" in the inspector settings. Support in
Firefox will be available when they implement it. Then compile your
project with -debug and haXe will output a .map file which contains the
debug information.
Let me know how it works for you! haXe is the first language I know to
implement JS source mapping, so there may be some issues.
Bruno
Bruno
--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
Did you enable source maps in the Chrome? (by clicking the little gear
button in the bottom right of the inspector and checking that setting)
If it is on, maybe there's some issue with Windows style paths.
Bruno
--
I'm on Windows 7 using Sublime to build. I see that my map files exists, it's referenced in my generated js file, and I've got the latest Chrome with Source Maps enabled. Am I missing something, because I can't get Chrome to grab my source map? There's no record of an attempt to download it from the network tab. Any help would be appreciated.
I'm on Windows 7 using Sublime to build. I see that my map files exists, it's referenced in my generated js file, and I've got the latest Chrome with Source Maps enabled. Am I missing something, because I can't get Chrome to grab my source map? There's no record of an attempt to download it from the network tab. Any help would be appreciated.
--
Hmmm... is there something obvious I'm missing. I enabled source maps in chrome, and am compiling with the -debug flag in HaXe. For some reason when I compile, the compiler doesn't generate a source map.
--
---
You received this message because you are subscribed to the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/groups/opt_out.