Hi Dimitri
I’ve put it on the todo list to make .babelrc enable-able globally, probably as
part of the Maker, so that should be done this weekend too
I did try Nashorn but I had non-trivial issues that I needed to look into - for
example, I have a Rhino debugger I’ve written (think
Hi Stefan
Great, I’m glad its working for you too :) Hopefully ES6 support something
that we can use to help generate a bit of excitement back into Qooxdoo and make
it more modern.
It’s great to see it getting used in big projects so soon, IMHO the core is
pretty stable but my main concern
BTW I missed you comment on this earlier - by profiling, do you mean of the
compilation process or injecting profiling statements into the generated code?
On 18/02/2016, 17:51, "Dimitri" wrote:
>I'm not a Node.js pro (I'm a JavaEE architect in fact :) so I'm not
Hi John,
I understood it as a means to profile QxCompiler. But even if Dimitri had
something else in mind, it probably would be useful to know where QxCompiler
spends most of it's time in order to focus on optimizing at the right place.
BWT, I am looking forward to trying QxCompiler myself,
>
>Slightly offtopic: did you try Nashorn with your server-side? Should be
>much faster and feature-rich. Besides, we are planning an opensource
>project - JavaScript console for JavaEE with qooxdoo frontend a la
>Playground. It would allow to author/run/manage server-side scripts,
>with support
That PR is withdrawn now in favour of this one, which has a much improved
commit history: https://github.com/qooxdoo/qooxdoo/pull/173
John
On 18/02/2016, 17:19, "John Spackman" wrote:
>Just done it :) https://github.com/qooxdoo/qooxdoo/pull/170
>
>It’s backwards