Notify application when JSXTransformer has completed processing JSX

[fleaflicker]

As first discussed in #1558 (comment) .

Use case: Application code is in app.js; react code is in file ui.jsx. In development, both are included along with JSXTransformer. There's no way for app.js to reliably reference components defined in ui.jsx. (In production, JSX is first translated, then all JS files are combined/compiled together, so this is not an issue.)

As noted in the above comment, there are workarounds.

[syranide]

Just a side-note, I really recommend that you use the jsx --watch util instead. JSXTransformer is inherently flawed with respect to script loading, use the jsx-tool and you have identical behavior for DEV and PROD (and also correct sources for all errors, in all browsers).

[zpao]

@RReverser if you're really interested in doing this, I don't mind. I think this is slightly more practical than #1995, but it still could encourage the wrong behavior. What do you think?

[RReverser]

@zpao Well, if you're going to combine functionality of react-tools and JSXTransformer into single place/file, then it doesn't make much sense to add any API changes before that. Or did I misunderstand you?

[zpao]

I think the combining might end up being a bit more of a convergence. These things overlap a lot with slight API differences. The other big difference is that JSXTransformer finds script tags. I was considering smoothing out API differences, then having JSXTransformer be the browserify override. Any new functionality we add to JSXTransformer now would in turn make it to the new place too.

[sophiebits]

If you need this, I believe you can add

<script type="text/jsx">
MyApp.init();
</script>

or similar after the external script tags and that will queue it correctly.