JaroslavTulach: /* Porting JavaFX to iOS */ - 2016-04-21 16:58:05

Porting JavaFX to iOS

←Older revision Revision as of 16:58, 21 April 2016
Line 5: Line 5:
== Porting [[JavaFX]] to [[iOS]] ==
== Porting [[JavaFX]] to [[iOS]] ==
-
In 2013 I was working with the [[Prague]] team responsible for porting [[JavaFX]] to [[iOS]]. Of course, for that one needs to have a [JVM]] and yes, there was one available. These days its code is [http://openjdk.java.net/projects/mobile/|open sourced as a OpenJDK subproject].
+
In 2013 I was working with the [[Prague]] team responsible for porting [[JavaFX]] to [[iOS]]. Of course, for that one needs to have a [JVM]] and yes, there was one we had access to: These days its code is [http://openjdk.java.net/projects/mobile/|open sourced as a OpenJDK subproject]. My employer seemed committed to the [[JDK]], but just in headless mode (remember the '''profiles''' of [[JDK]]8 being really hot at that time and btw. they are still the most coolest thing about [[JDK]]8 in my opinion). However my employer's attitude towards UI hasn't been that clear. While the Prague team was working hard on [[JavaFX]] port, the performance wasn't all that great. At that moment [[I]] stepped in and and offered ''lightweight JavaFX''.
 +
 
 +
 
[[TBD]]
[[TBD]]

JaroslavTulach at 16:50, 21 April 2016 - 2016-04-21 16:50:34

←Older revision Revision as of 16:50, 21 April 2016
Line 5: Line 5:
== Porting [[JavaFX]] to [[iOS]] ==
== Porting [[JavaFX]] to [[iOS]] ==
-
In 2013 I was working with the [[Prague]] team responsible for porting [[JavaFX]] to [[iOS]]. Of course, for that one needs to have a [JVM]] and yes, there was one available. These days its code is [http://openjdk.java.net/projects/mobile/][open sourced as a OpenJDK subproject].
+
In 2013 I was working with the [[Prague]] team responsible for porting [[JavaFX]] to [[iOS]]. Of course, for that one needs to have a [JVM]] and yes, there was one available. These days its code is [http://openjdk.java.net/projects/mobile/|open sourced as a OpenJDK subproject].
[[TBD]]
[[TBD]]

JaroslavTulach at 16:50, 21 April 2016 - 2016-04-21 16:50:12

←Older revision Revision as of 16:50, 21 April 2016
Line 1: Line 1:
Whenever one is bringing two systems together, it is good to have a [[common ground]]. We had one when we sneaked [[NetBeans]] under [[JDeveloper]] (read it [[JDeveloper|here]]). Now we have [[DukeScript]] - the [[wikipedia:Lingua_franca|lingua franca]] between [[TeaVM]], [[Bck2Brwsr]] [[VM]], [[DlvkBrwsr]], and more.
Whenever one is bringing two systems together, it is good to have a [[common ground]]. We had one when we sneaked [[NetBeans]] under [[JDeveloper]] (read it [[JDeveloper|here]]). Now we have [[DukeScript]] - the [[wikipedia:Lingua_franca|lingua franca]] between [[TeaVM]], [[Bck2Brwsr]] [[VM]], [[DlvkBrwsr]], and more.
-
There was a [[NetBeans]] Day Conference at Munich on Mar 31, 2016. Thomas demonstrated how easy it is to embed [[OracleJET]] into existing [[Swing]]/[[JavaFX]] application via [[JavaFX]] [[WebView]] - at that moment I hurried up to the stage and showed that [[DukeScript]] core has support for that as well and that it has so many benefits that it is clear everybody should be using the [[JavaScriptBody]] annotation all the time. However Thomas hasn't got my message - later in a pub [[I]] realized why: because when talking about [[DukeScript]] [[I]] implicitly assume people understand that it is the [[common ground]] for integration between [[Java]] and [[JavaScript]]. They don't. But they should, please read my explanation!
+
There was a [[NetBeans]] Day Conference at Munich on Mar 31, 2016. Thomas demonstrated how easy it is to embed [[OracleJET]] into existing [[Swing]]/[[JavaFX]] application via [[JavaFX]] [[WebView]] - at that moment I hurried up to the stage and showed that [[DukeScript]] core has support for that as well and that it has so many benefits that it is clear everybody should be using the [[JavaScriptBody]] annotation all the time. However Thomas hasn't got my message - later in a pub [[I]] realized why: because when talking about [[DukeScript]] [[I]] implicitly assume people understand that it is the [[common ground]] for integration between [[Java]] and [[JavaScript]]. They don't. But they should as I am going to explain now...
== Porting [[JavaFX]] to [[iOS]] ==
== Porting [[JavaFX]] to [[iOS]] ==
 +
 +
In 2013 I was working with the [[Prague]] team responsible for porting [[JavaFX]] to [[iOS]]. Of course, for that one needs to have a [JVM]] and yes, there was one available. These days its code is [http://openjdk.java.net/projects/mobile/][open sourced as a OpenJDK subproject].
[[TBD]]
[[TBD]]

JaroslavTulach at 15:42, 20 April 2016 - 2016-04-20 15:42:11

←Older revision Revision as of 15:42, 20 April 2016
Line 1: Line 1:
Whenever one is bringing two systems together, it is good to have a [[common ground]]. We had one when we sneaked [[NetBeans]] under [[JDeveloper]] (read it [[JDeveloper|here]]). Now we have [[DukeScript]] - the [[wikipedia:Lingua_franca|lingua franca]] between [[TeaVM]], [[Bck2Brwsr]] [[VM]], [[DlvkBrwsr]], and more.
Whenever one is bringing two systems together, it is good to have a [[common ground]]. We had one when we sneaked [[NetBeans]] under [[JDeveloper]] (read it [[JDeveloper|here]]). Now we have [[DukeScript]] - the [[wikipedia:Lingua_franca|lingua franca]] between [[TeaVM]], [[Bck2Brwsr]] [[VM]], [[DlvkBrwsr]], and more.
-
There was a [[NetBeans]] Day Conference at Munich on Mar 31, 2016. Thomas demonstrated how easy it is to embed [[OracleJET]] into existing [[Swing]]/[[JavaFX]] application via [[JavaFX]] [[WebView]] - at that moment I hurried up to the stage and showed that [[DukeScript]] core has support for that as well and that it has so many benefits that it is clear everybody should be using the [[JavaScriptBody]] annotation all the time. However Thomas hasn't got my message - later in a pub [[I]] realized why: because when talking about [[DukeScript]] [[I]] implicitly assume people understand that it is the [[common ground]] for integration between [[Java]] and [[JavaScript]]. Hear my explanation!
+
There was a [[NetBeans]] Day Conference at Munich on Mar 31, 2016. Thomas demonstrated how easy it is to embed [[OracleJET]] into existing [[Swing]]/[[JavaFX]] application via [[JavaFX]] [[WebView]] - at that moment I hurried up to the stage and showed that [[DukeScript]] core has support for that as well and that it has so many benefits that it is clear everybody should be using the [[JavaScriptBody]] annotation all the time. However Thomas hasn't got my message - later in a pub [[I]] realized why: because when talking about [[DukeScript]] [[I]] implicitly assume people understand that it is the [[common ground]] for integration between [[Java]] and [[JavaScript]]. They don't. But they should, please read my explanation!
== Porting [[JavaFX]] to [[iOS]] ==
== Porting [[JavaFX]] to [[iOS]] ==

JaroslavTulach at 15:41, 20 April 2016 - 2016-04-20 15:41:02

←Older revision Revision as of 15:41, 20 April 2016
Line 1: Line 1:
-
Whenever one is bringing two systems together, it is good to have a [[common ground]]. We had one when we sneaked [[NetBeans]] under [[JDeveloper]] (read it [[JDeveloper|here]]). Now we have [[DukeScript]] - the [[wikipedia:Lingua_franca|lingua franca]] between [[TeaVM]], [[Bck2Brwsr]] [[VM]], [[DlvkBrwsr]], etc.
+
Whenever one is bringing two systems together, it is good to have a [[common ground]]. We had one when we sneaked [[NetBeans]] under [[JDeveloper]] (read it [[JDeveloper|here]]). Now we have [[DukeScript]] - the [[wikipedia:Lingua_franca|lingua franca]] between [[TeaVM]], [[Bck2Brwsr]] [[VM]], [[DlvkBrwsr]], and more.
 +
 
 +
There was a [[NetBeans]] Day Conference at Munich on Mar 31, 2016. Thomas demonstrated how easy it is to embed [[OracleJET]] into existing [[Swing]]/[[JavaFX]] application via [[JavaFX]] [[WebView]] - at that moment I hurried up to the stage and showed that [[DukeScript]] core has support for that as well and that it has so many benefits that it is clear everybody should be using the [[JavaScriptBody]] annotation all the time. However Thomas hasn't got my message - later in a pub [[I]] realized why: because when talking about [[DukeScript]] [[I]] implicitly assume people understand that it is the [[common ground]] for integration between [[Java]] and [[JavaScript]]. Hear my explanation!
 +
 
 +
== Porting [[JavaFX]] to [[iOS]] ==
 +
 
 +
[[TBD]]
 +
 
 +
== The [[Java]]/[[JavaScript]] Bridge ==
 +
 
 +
Which one?
 +
 
 +
== Lightweight Protocol ==
 +
 
 +
JavaScriptBody and callbacks.

JaroslavTulach: New page: Whenever one is bringing two systems together, it is good to have a common ground. We had one when we sneaked NetBeans under JDeveloper (read it here). Now we ha... - 2014-03-20 14:17:41

New page: Whenever one is bringing two systems together, it is good to have a common ground. We had one when we sneaked NetBeans under JDeveloper (read it here). Now we ha...

New page

Whenever one is bringing two systems together, it is good to have a [[common ground]]. We had one when we sneaked [[NetBeans]] under [[JDeveloper]] (read it [[JDeveloper|here]]). Now we have [[DukeScript]] - the [[wikipedia:Lingua_franca|lingua franca]] between [[TeaVM]], [[Bck2Brwsr]] [[VM]], [[DlvkBrwsr]], etc.