flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roland Zwaga <rol...@stackandheap.com>
Subject Re: [ASJS] debugging output JS?
Date Mon, 28 Jan 2013 10:00:29 GMT
On 28 January 2013 10:51, Erik de Bruin <erik@ixsoftware.nl> wrote:

> Hi Roland (et al.),
> No, I don't think you misunderstood, you seem to grok our positions
> correctly.
> What I don't see in the 'debug JS' approach is what do you do with the
> bugs you find in JS? Any changes you make in the JS will get
> overwritten the next time you compile the AS, correct? Or am I missing
> something?

Oh no, changing the generated JS would be futile, but having clear access to
through, for example, source maps would be really important for being able
pinpoint what is going wrong. I'm sure that once Apache Flex starts
churning out
projects that are being cross-compiled we're going to run into edge cases
where the
generated JS doesn't work, or doesn't work as expected. And especially in
the latter
case you'd probably want to be able to play around with the JS to see what
the problem
is exactly.
Am I making sense?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message