Hello all;
I'm developing AsciidocFX https://github.com/asciidocfx/AsciidocFX .
Everything is good with JavaFX but I have some trouble of it's threading
model.
My case is;
AsciidocFX converts AsciiDoc documents to another formats (html, docbook,
etc.) with asciidoctor.js using a WebView
Am Donnerstag, 6. August 2015, 12:25:19 schrieb Rahman USTA:
Hello all;
I'm developing AsciidocFX https://github.com/asciidocfx/AsciidocFX .
Everything is good with JavaFX but I have some trouble of it's threading
model.
My case is;
AsciidocFX converts AsciiDoc documents to another
That seems like a roundabout way to do things.
The web tells me: The asciidoctor.js project is a direct port of
Asciidoctor from Ruby to JavaScript using the Opal Ruby-to-JavaScript cross
compiler
Why don't you use JRuby and run the original Asciidoctor code directly in a
background thread?
@Mike
JRuby brings me ~ +30 MB. I tried to use Nashorn also but it is so slow.
I'm thinking to continue with WebView.
The question is why there is HTML 5 Web Workers. Why there is no like that
for JavaFX threading model.
@Jens
Expensiveness comes from JavaScript code that runs on UI thread.
Am Donnerstag, 6. August 2015, 14:00:27 schrieb Rahman USTA:
@Mike
JRuby brings me ~ +30 MB. I tried to use Nashorn also but it is so slow.
I'm thinking to continue with WebView.
The question is why there is HTML 5 Web Workers. Why there is no like that
for JavaFX threading model.
Jens;
executeScript must be run on JavaFX Application Thread, and execution of my
script takes long time. There is an unavoidable freezing case if your
script takes long time.
CompletableFuture can't help us because the issue arise from JavaScript
execution.
2015-08-06 14:17 GMT+03:00 Jens
