The OL compiler has all the info it needs to do this, as you can see if you compile in debug mode (there are file/line directives as comments in the output). SMOP to output that information to a source map when in non-debug.
On 2011-08-10, at 06:50, Raju Bitter wrote: > Use case #2 refers to the use cases listed here: > https://wiki.mozilla.org/DevTools/Features/SourceMap > > On Wed, Aug 10, 2011 at 3:49 PM, Raju Bitter > <[email protected]> wrote: >> Mozilla and the Webkit team are planning to support debugging of >> minified or generated JS in the browser using the SourceMap standard: >> http://www.infoq.com/news/2011/08/debug-languages-on-javascript-vm >> >> Google built SourceMap support into Google Closure (Closure JavaScript >> compiler), and the Google Closure Inspector. >> "Closure Inspector is an extension to Firebug, the Firefox debugger >> extension. Closure Inspector adds three powerful features to Firebug: >> source mapping, improved stack trace display, and unit test >> integration." >> http://code.google.com/closure/compiler/docs/inspector.html >> >> Use case #2 applies to the way OL generates JS: >> Case 2: Languages which compile to JavaScript >> You can start with an original file which contains any language that >> compiles to JS (for example, CoffeeScript). Any logged output or >> uncaught errors will refer back to the original file, rather than the >> generated JS file which is actually being executed. >> >> If the OpenLaszlo compiler would generate a SourceMap file, developers >> could use Firefox and Webkit to jump back to the original line of LZX >> code when running into an error in the DHTML runtime. >> >> Links: >> https://wiki.mozilla.org/DevTools/Features/SourceMap >> https://bugzilla.mozilla.org/show_bug.cgi?id=618650 >> https://bugs.webkit.org/show_bug.cgi?id=63940 >> https://docs.google.com/document/d/14AWiLDDxEuLaWuyG0X6deLRufrvxRu8HBP0LNJwvRZw/edit?hl=en_US&pli=1 >>
