This is awesome news! Congrats
Sent from Objectwheel Mike
On Aug 6, 2015, at 1:11 PM, Tai Hu tai...@veroanalytics.com wrote:
Hi all,
I am preparing our product (built in JavaFX 8) for submission to Apple
Mac Store. All code signing and self-contained installer generation are done.
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?
Currently the Mac App Store support for java packager does not support a
click-through license. One could be added if a web-bug feature request was
posted, and we could add it to the queue. We do support click-through licenses
for .DMG and .PKG distributions on mac, just not MAS right now.
Danno,
Thanks so much for the information. Could you show a sample about how to
include a click-thought license in my build? Right now I have entire build
process set up and could successfully build all DMG, PKG and PKG_MacAppStore
and signed by our Developer certificate. What should I do
Hi all,
As you might be aware, JEP 253 is all about getting private JavaFX UI
control and CSS APIs out into the public. You can read all about JEP 253
at [1]. This JEP is split into three sub-projects:
1) Make UI control skins into public APIs
2) Improve support for input mapping
3) Review
Hi all. In April of this year a discussion began when news broke that
with JDK 9 access to private com.sun.* APIs would be disappearing [1]. A
while back I posted a request to openjfx-dev for people to send me their
JDeps output so that it could be analysed and used to inform our
decisions
@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
Hi all, I'm running a java application on iMX.6 (Freescale) with javafx
within it. The JVM crashes after some time. I have two files:
hs_err_pid1101.log (few kbytes) and core (this is big, 500mb~). Where I can
get help with that crashes? Should I provide the core dump here or shold be
delivered to
Hi all,
I'm running applications on Freescale's iMX.6 using JavaFX. It's known
that it doesn't uses X but directly access the framebuffer instead, so
x11vnc doesn't applies. I need to export the video input/output as VNC
does.
Does anybody knows an alternative solution for this?
Best regards,
-
On 8/6/15, 9:36 AM, Daniel. wrote:
Hi all,
I'm running applications on Freescale's iMX.6 using JavaFX. It's known
that it doesn't uses X but directly access the framebuffer instead, so
x11vnc doesn't applies. I need to export the video input/output as VNC
does.
Does anybody knows an
I agree. Please file a bug.
-- Kevin
Tom Eugelink wrote:
Indeed, this exception put me on the wrong track, trying to figure out
why the test was failing based on the exception, while I was just
asserting the wrong property.
I now also understand what it is trying to tell me. And I must
Exactly.
-- Kevin
Phil Race wrote:
I am going to guess its because when you get real close to release and
start building
candidates for release the build string no longer has EA in it, and
someone might
mistakenly think it is an actual confirmed FCS build you can use in
production.
That is
16 matches
Mail list logo