Re: Future of JavaFX

2015-12-01 Thread info
If it is not a part of OpenJDK/Oracle JDK it will not work. Whether Oracle itself maintains the code doesn't really matter I think, but they have to put support and development in it. To me another downside if Oracle would suspend further development is that any statements made by Oracle se

Re: Future of JavaFX

2015-12-01 Thread Felix Bembrick
Well, it is the official Swing replacement but look at Java 9 and you won't see many if any enhancements to JavaFX. The point is Oracle has no interest in desktop software other than maintaining any existing support contracts. I don't even think Oracle wants JavaFX so it would be better for eve

Re: Future of JavaFX

2015-12-01 Thread Peter Pilgrim
Hi All I find it remarkable to see that this debate about innovation-versus-maintenance is similar to the one going on in the Java EE space. See https://java.net/projects/javaee-spec/lists/users/archive/2015-01/message/48 - Many Java EE experts, including myself, are now looking at the application

Re: Future of JavaFX

2015-12-01 Thread Felix Bembrick
Is it really true that *all* of JavaFX is open source? Even if it is, if I wanted to say take some aspects of the product in a radical new direction, wouldn't someone from Oracle have to approve the changes? If yes, then only Oracle can bring the big enhancements that are necessary which we kno

Re: Future of JavaFX

2015-12-01 Thread Mario Torre
2015-12-01 14:03 GMT+01:00 Felix Bembrick : > Is it really true that *all* of JavaFX is open source? > > Even if it is, if I wanted to say take some aspects of the product in a > radical new direction, wouldn't someone from Oracle have to approve the > changes? > > If yes, then only Oracle can br

Re: Future of JavaFX

2015-12-01 Thread Johan Vos
Hi Dirk, all, Although this person from Codename One attacked me a few times before (using words like we're selling snake oil), I tried to ignore it. This is very uncommon for the Java community. In the Java community, we have different views, we prefer different technologies, but we show at least

Re: Future of JavaFX

2015-12-01 Thread Johan Vos
As far as I know, all of JavaFX is open source indeed. If someone wants to make a big change, e.g. create another rendering pipeline, it is very well possible to do so. I would recommend submitting that work back to OpenJFX, by following the same procedures for committing to the OpenJDK project, b

Re: Future of JavaFX

2015-12-01 Thread Felix Bembrick
I agree with Johan that there is a rich and vibrant JavaFX community and most examples of its adoption are behind corporate firewalls. But Johan, why would Oracle build a "JavaFX ecosystem" within Oracle and spend millions on a product that earns them nothing? Surely that is not sustainable. An

Re: Future of JavaFX

2015-12-01 Thread dalibor topic
On 01.12.2015 14:22, Mario Torre wrote: Btw, as a general note, I always find discussing about how impossible any contribution is *without* first trying to contribute anything a real waste of time. For mailing list environments with a bad signal/noise ratio, I suggest applying https://joeyh.

gradle 2.9 is now the default in FX 9-dev

2015-12-01 Thread Kevin Rushforth
The switch to gradle 2.9 has been pushed to 9-dev as indicated in [1]. Anyone who has not yet updated to gradle 2.9 should do so within the next two weeks. -- Kevin [1] http://mail.openjdk.java.net/pipermail/openjfx-dev/2015-November/018210.html

Re: Future of JavaFX

2015-12-01 Thread Peter Pilgrim
Hi All On 1 December 2015 at 13:27, Johan Vos wrote: > Hi Dirk, all, > > Although this person from Codename One attacked me a few times before > (using words like we're selling snake oil), I tried to ignore it. This is > very uncommon for the Java community. In the Java community, we have > diffe

Re: Future of JavaFX

2015-12-01 Thread Peter Pilgrim
How timely as I just posted that response and Dalibor's news just arrived in the my inbox within 1 minute ... #TLDR JDK 9 will arrive 6 months later than expected 23rd March 2017 ... so FX people go to work, really go work. On 1 December 2015 at 17:12, Peter Pilgrim wrote: > Hi All > > On 1 De

RE: Future of JavaFX

2015-12-01 Thread Markus KARG
I assume you already opened a JIRA ticket and filed a reproducible test case, so Oracle can fix the issue ASAP? ;-) -Markus -Original Message- From: openjfx-dev [mailto:openjfx-dev-boun...@openjdk.java.net] On Behalf Of Daniel. Sent: Montag, 30. November 2015 22:49 To: Florian Brunner Cc

RE: Future of JavaFX

2015-12-01 Thread Markus KARG
Speaking of promotion an VW, does it make the Golf an outdated car just because they stopped TV marketing in Germany because their sales is running quite well still? ;-) -Original Message- From: openjfx-dev [mailto:openjfx-dev-boun...@openjdk.java.net] On Behalf Of Tom Eugelink Sent: Mo

RE: Future of JavaFX

2015-12-01 Thread Markus KARG
With respect to TeamFX, the better question is: Are there plans to further open the project so third party has an easier channel to contribute without the hazzle of contributor agreements, JIRA accounts, and so on? -Original Message- From: openjfx-dev [mailto:openjfx-dev-boun...@openjdk.ja

Re: Future of JavaFX

2015-12-01 Thread dalibor topic
On 01.12.2015 18:35, Markus KARG wrote: With respect to TeamFX, the better question is: Are there plans to further open the project so third party has an easier channel to contribute without the hazzle of contributor agreements "Like many other open-source communities, the OpenJDK Community req

RE: Future of JavaFX

2015-12-01 Thread Markus KARG
I wonder why I was able to jointly assign my copyright with a lot of other open source projects without having to sign papers, sent them in by fax, wait for a written agreement, and pray to get a JIRA account... ;-) See, I talked to a real lot of former JavaFX contributors in the past weeks (visit

Re: Future of JavaFX

2015-12-01 Thread Hervé Girod
Things are not different for Apache projects. Google does not accept any external contributions. The Linux kernel development is very tightly controlled. We should stop considering that widespread open source policies are only a problem with JavaFX. These policies are in place for a reason. Her

Re: Future of JavaFX

2015-12-01 Thread dalibor topic
On 01.12.2015 20:13, Markus KARG wrote: anymore or AT LEAST vote and comment on existing tickets. Is the JavaFX team clear about how many contributors you lost by that policy? I think the number you're looking for is zero, judging by the number of 'Contributed-by' changesets in the rt reposito

Re: Future of JavaFX

2015-12-01 Thread Tomas Mikula
The fact that there are other projects with equally bad or worse contribution process does not make the JavaFX's any less bad. Yes, there should be (strict) policies regarding code quality. The rest of the process should be as easy as opening a pull request. Tomas On Tue, Dec 1, 2015 at 2:18 PM,

RE: Future of JavaFX

2015-12-01 Thread Markus KARG
We should ask ourselfs whether we want more contributions or not. We will not get them until we change something. Most contributors in the Open Source just want to drop a bug report or a feature or two, and multiplied by the number of those guys, this is a lot of stuff. Only few contributors are

RE: Future of JavaFX

2015-12-01 Thread Markus KARG
Dalibor, exactly what I expected to hear from Oracle! You count the number of input that actually made it through exactly that bureaucracy I am talking about holding back contributors! Well done! Certainly the number is zero, that's what I try to tell you. I actually talk about those people that

Re: Future of JavaFX

2015-12-01 Thread Tomas Mikula
The review process for external contributions does not even have to be different from the internal review process. There can be a virtual organization on GitHub called "Oracle CLA signatories". After a pull request has been reviewed, all that the OpenJFX committer has to do before merging is to che

RE: Future of JavaFX

2015-12-01 Thread Markus KARG
Too bad that Github cannot fork mercurial repos. It would be interesting to see the real number of pull requests such a fork would gain. Maybe Dalibor is right and we would end up with zero? ;-) -Markus From: Tomas Mikula [mailto:tomas.mik...@gmail.com] Sent: Dienstag, 1. Dezember 2015 23:0

Re: Future of JavaFX

2015-12-01 Thread Tomas Mikula
The proposed strategy also applies to bitbucket, which does have mercurial support ;) On Tue, Dec 1, 2015 at 5:12 PM, Markus KARG wrote: > Too bad that Github cannot fork mercurial repos. It would be interesting > to see the real number of pull requests such a fork would gain. Maybe > Dalibor is

Re: Future of JavaFX

2015-12-01 Thread Donald Smith
Check in with the Adopt OpenJDK list, I know there's a few people who pull source OpenJDK into Github -- it can't be that difficult. I'm sure someone can help. - Don On 01/12/2015 5:16 PM, Tomas Mikula wrote: The proposed strategy also applies to bitbucket, which does have mercurial support

RE: Future of JavaFX

2015-12-01 Thread Daniel Kraus
Volkswagen is doing a lot of research with JavaFX. For more than two years now, it is their technology of choice for rapid HMI prototyping. The have developed a framework–namely Tappas–entirely written in Java/JavaFX, which already runs on embedded hardware, featuring a 3D map renderer.[1][2][3] P

Re: Future of JavaFX

2015-12-01 Thread Jeff Hain
Felix Bembrick wrote: >it makes them no money >In my opinion, JavaFX should be jettisoned from the JDK Like AWT or Swing, it plays in favor of Java adoption by people looking for a portable way of doing something as simple as lighting up a pixel - which are still, after all these years, quite sca

Re: Future of JavaFX

2015-12-01 Thread Kevin Rushforth
Just to chime in on a couple of points that have been raised in this discussion... * We are interested in working with the OpenJFX community to improve JavaFX. In particular: if you find a bug, file it (via bugs.java.com if you don't have a JBS account); if you want to contribute a patch to fi