JavaFX website

Discussion:

JavaFX website

Johan Vos

2018-09-04 07:01:59 UTC

It has been mentioned a number of times that JavaFX would benefit from a
JavaFX website.
I see a number of options that fall in the category website:

1. A set of pages with details on what OpenJFX is, how to build, where to
download and get release notes, how to contribute, roadmap,... That is what
I believe can perfectly be done in the OpenJFX wiki. It can be the
reference manual

2. A set of pages targeting new and existing JavaFX developers, with a
focus on where to download, how to get started (maven/gradle/IDE's), where
to get docs/tutorials and probably with some links to third party libraries
(free/commercial). This is sort of the user manual.

3. A highly interactive community site, gathering tweets/blog posts etc,
more or less similar to what James Weaver and Gerrit Grunwald did years ago.

For 1: I think this is up to us (OpenJFX committers) to maintain and
improve. It will also benefit the people here.

For 2: This is the most important thing, I believe. It would be great if a
number of people from this list step up to organize this. It can be a
static website, a github page, or anything else. I don't think this
strictly belongs under OpenJFX (which I consider to be the technical
development umbrella) but it's extremely important to have.
I think this is a perfect opportunity for people and companies who want to
get more active in JavaFX to get involved in.

For 3: That would be nice, but I think it's too ambitious for now. I would
be happy with a static, simple, clear website.

- Johan

Miroslav Nachev

2018-09-04 07:13:35 UTC

Permalink

4. Online demonstration of graphical controls and other capabilities -
basic and extra from the community.

Post by Johan Vos
It has been mentioned a number of times that JavaFX would benefit from a
JavaFX website.
1. A set of pages with details on what OpenJFX is, how to build, where to
download and get release notes, how to contribute, roadmap,... That is what
I believe can perfectly be done in the OpenJFX wiki. It can be the
reference manual
2. A set of pages targeting new and existing JavaFX developers, with a
focus on where to download, how to get started (maven/gradle/IDE's), where
to get docs/tutorials and probably with some links to third party libraries
(free/commercial). This is sort of the user manual.
3. A highly interactive community site, gathering tweets/blog posts etc,
more or less similar to what James Weaver and Gerrit Grunwald did years ago.
For 1: I think this is up to us (OpenJFX committers) to maintain and
improve. It will also benefit the people here.
For 2: This is the most important thing, I believe. It would be great if a
number of people from this list step up to organize this. It can be a
static website, a github page, or anything else. I don't think this
strictly belongs under OpenJFX (which I consider to be the technical
development umbrella) but it's extremely important to have.
I think this is a perfect opportunity for people and companies who want to
get more active in JavaFX to get involved in.
For 3: That would be nice, but I think it's too ambitious for now. I would
be happy with a static, simple, clear website.
- Johan

Michael Ennen

2018-09-04 07:16:52 UTC

Permalink

Johan,

I just wanted to remind you (and everyone) that Github offers a Wiki feature
so we have a nice way to house at least some documentation (probably mostly
related to actually working on OpenJFX itself) already.

I think 3.) is somewhat pie-in-the-sky and it is my humble opinion that time
would be better spent documenting for other prospective developer's how
we (the contributors) actually work on JavaFX. How do we set up IDEs,
configure build systems, debug native code, etc. etc.

I am trying to make setting up a local dev environment as painless
as possible on Windows for working on JavaFX and there is a tie-in
to that effort with having Appveyor scripts that share the same build/setup
logic. I have made some progress thereof, I want to make more.

Cheers,
Michael Ennen

Abossolo Foh Guy

2018-09-04 07:23:54 UTC

Permalink

Hi Michael,
Could everybody access to the Wiki and modify it ?
Guy.
--------------------------------

Post by Michael Ennen
Johan,
I just wanted to remind you (and everyone) that Github offers a Wiki feature
so we have a nice way to house at least some documentation (probably mostly
related to actually working on OpenJFX itself) already.
I think 3.) is somewhat pie-in-the-sky and it is my humble opinion that time
would be better spent documenting for other prospective developer's how
we (the contributors) actually work on JavaFX. How do we set up IDEs,
configure build systems, debug native code, etc. etc.
I am trying to make setting up a local dev environment as painless
as possible on Windows for working on JavaFX and there is a tie-in
to that effort with having Appveyor scripts that share the same build/setup
logic. I have made some progress thereof, I want to make more.
Cheers,
Michael Ennen

Post by Johan Vos
It has been mentioned a number of times that JavaFX would benefit from a
JavaFX website.
1. A set of pages with details on what OpenJFX is, how to build, where to
download and get release notes, how to contribute, roadmap,... That is what
I believe can perfectly be done in the OpenJFX wiki. It can be the
reference manual
2. A set of pages targeting new and existing JavaFX developers, with a
focus on where to download, how to get started (maven/gradle/IDE's), where
to get docs/tutorials and probably with some links to third party libraries
(free/commercial). This is sort of the user manual.
3. A highly interactive community site, gathering tweets/blog posts etc,
more or less similar to what James Weaver and Gerrit Grunwald did
years
ago.
For 1: I think this is up to us (OpenJFX committers) to maintain and
improve. It will also benefit the people here.
For 2: This is the most important thing, I believe. It would be great if a
number of people from this list step up to organize this. It can be a
static website, a github page, or anything else. I don't think this
strictly belongs under OpenJFX (which I consider to be the technical
development umbrella) but it's extremely important to have.
I think this is a perfect opportunity for people and companies who want to
get more active in JavaFX to get involved in.
For 3: That would be nice, but I think it's too ambitious for now. I would
be happy with a static, simple, clear website.
- Johan

--
Abossolo Foh Guy
71 rue Guy de Maupassant
69500 Bron

06 87 01 82 27
04 72 81 89 46

Abossolo Foh Guy

2018-09-19 21:03:05 UTC

Permalink

Hi,

May be my first bug report in 2008 :-)
I felt very pride when I recieved this mail, even thougt it was a robot
answer :-)

Dear Java Developer,
Thank you for your interest in improving the quality of Java Technology. Your report has been assigned an internal review ID of 1379474, which is NOT visible on the Sun Developer Network (SDN). Please be aware that the large volume of reports we receive sometimes prevents us from responding individually to each message. If the information is determined to be a new Bug or RFE, or a duplicate of a known Bug or RFE, you will receive a followup email containing a seven digit bug number. You may search for, view, or vote for this bug in the Bug Database at http://bugs.sun.com/. If you just reported an issue that could have a major impact on your project and require a timely response, please consider purchasing one of the support offerings described at http://developers.sun.com/services/. The Sun Developer Network (http://developers.sun.com) is a free service that Sun offers. To join, visit http://developers.sun.com/global/join_sdn.html. For a limited time, SDN members can obtain

fully
licensed Java IDEs for web and enterprise development. More information is at http://developers.sun.com/prodtech/javatools/free/. Thank you for using our bug submit page.

Regards, Java Developer Bug Report Review Team

But since some years, no more information.

How to know the status of a bug report ?

I'm present (trying to be not "noisy") in the JDK and JFX lists since I
discovered that one of my bug report (JDK-8133864) was treated without a
feedback from JBS.

I saw that the bug was corrected only after installing a new Java
version.

I never received a bug ID ?

Could bug reporter have at least an automatic feedback of the status of
his bug report.

Best regards.

Kevin Rushforth

2018-09-19 22:19:06 UTC

Permalink

Back in 2015, when the bug in question was filed, there was no
additional communication sent. Today you should receive an email once a
bug is moved to the JDK project, so you can track it.

-- Kevin

Post by Abossolo Foh Guy
Hi,
May be my first bug report in 2008 :-)
I felt very pride when I recieved this mail, even thougt it was a robot
answer :-)

fully
licensed Java IDEs for web and enterprise development. More information is at http://developers.sun.com/prodtech/javatools/free/. Thank you for using our bug submit page.

Regards, Java Developer Bug Report Review Team

But since some years, no more information.
How to know the status of a bug report ?
I'm present (trying to be not "noisy") in the JDK and JFX lists since I
discovered that one of my bug report (JDK-8133864) was treated without a
feedback from JBS.
I saw that the bug was corrected only after installing a new Java
version.
I never received a bug ID ?
Could bug reporter have at least an automatic feedback of the status of
his bug report.
Best regards.

Abossolo Foh Guy

2018-09-20 20:16:22 UTC

Permalink

Thanks a lot.

- Guy.

Post by Kevin Rushforth
Back in 2015, when the bug in question was filed, there was no
additional communication sent. Today you should receive an email once
a bug is moved to the JDK project, so you can track it.
-- Kevin

Post by Abossolo Foh Guy
Hi,
May be my first bug report in 2008 :-)
I felt very pride when I recieved this mail, even thougt it was a robot
answer :-)

Dear Java Developer,
Thank you for your interest in improving the quality of Java
Technology. Your report has been assigned an internal review ID of
1379474, which is NOT visible on the Sun Developer Network (SDN).
Please be aware that the large volume of reports we receive sometimes
prevents us from responding individually to each message. If the
information is determined to be a new Bug or RFE, or a duplicate of a
known Bug or RFE, you will receive a followup email containing a
seven digit bug number. You may search for, view, or vote for this
bug in the Bug Database at http://bugs.sun.com/. If you just reported
an issue that could have a major impact on your project and require a
timely response, please consider purchasing one of the support
offerings described at http://developers.sun.com/services/. The Sun
Developer Network (http://developers.sun.com) is a free service that
Sun offers. To join, visit
http://developers.sun.com/global/join_sdn.html. For a limited time,
SDN members can obtain

fully
licensed Java IDEs for web and enterprise development. More
information is at http://developers.sun.com/prodtech/javatools/free/.
Thank you for using our bug submit page.

Regards, Java Developer Bug Report Review Team

But since some years, no more information.
How to know the status of a bug report ?
I'm present (trying to be not "noisy") in the JDK and JFX lists since I
discovered that one of my bug report (JDK-8133864) was treated without a
feedback from JBS.
I saw that the bug was corrected only after installing a new Java
version.
I never received a bug ID ?
Could bug reporter have at least an automatic feedback of the status of
his bug report.
Best regards.

Nir Lisker

2018-09-04 08:18:01 UTC

Permalink

1. Yes. The OpenJFX wiki is editable only by specific people (or only
Kevin) and it requires a lot of updating. We need either to be able to
submit changes to it, or to use the GitHub wiki which is collaborative by
design, in which case we need to hide the OpenJFX wiki to avoid confusion.

2. Yes. The tutorials [1] are slightly outdated (and SceneBuilder should
disappear from there ASAP and point to Gluon). I don't know who controls
those pages.

3. No. There's not enough traction. Jonathan Giles collects some "links of
the week" and the semi-zombified /r/JavaFX subreddit is enough to indicate
that we shouldn't invest yet in this direction.

[1] https://docs.oracle.com/javase/8/javase-clienttechnologies.htm

- Nir

Kevin Rushforth

2018-09-04 12:48:50 UTC

Permalink

1. The OpenJFX Wiki on openjdk.java.net is ideal for maintaining pages
related to the Project itself. This can be supplemented by other Wikis.
As for access, any OpenJFX Project Author (or Committer) can have write
access to the Wiki. Just let me know if you want access, but it isn't
activated yet.

2. This is where the community could really help as noted by Johan and
others. The tutorials are indeed out of date. If you want to file a JBS
bug and assign it to me, I can see what needs to be done to either
correct (if simple) or archive pages that are so out of date as to be
useless (or worse, misleading).

-- Kevin

Post by Nir Lisker
1. Yes. The OpenJFX wiki is editable only by specific people (or only
Kevin) and it requires a lot of updating. We need either to be able to
submit changes to it, or to use the GitHub wiki which is collaborative by
design, in which case we need to hide the OpenJFX wiki to avoid confusion.
2. Yes. The tutorials [1] are slightly outdated (and SceneBuilder should
disappear from there ASAP and point to Gluon). I don't know who controls
those pages.
3. No. There's not enough traction. Jonathan Giles collects some "links of
the week" and the semi-zombified /r/JavaFX subreddit is enough to indicate
that we shouldn't invest yet in this direction.
[1] https://docs.oracle.com/javase/8/javase-clienttechnologies.htm
- Nir

Nir Lisker

2018-09-04 13:54:27 UTC

Permalink

1. I would like access, thanks. I'll be able to update the Eclipse
instructions and some of the Windows build instructions.

2. I submitted https://bugs.openjdk.java.net/browse/JDK-8210360. It's going
to take a large effort to go over every page there and see what needs
changing. If enough people join the task we could (and should) have it
updated for openjfx12.

Post by Kevin Rushforth
1. The OpenJFX Wiki on openjdk.java.net is ideal for maintaining pages
related to the Project itself. This can be supplemented by other Wikis.
As for access, any OpenJFX Project Author (or Committer) can have write
access to the Wiki. Just let me know if you want access, but it isn't
activated yet.
2. This is where the community could really help as noted by Johan and
others. The tutorials are indeed out of date. If you want to file a JBS
bug and assign it to me, I can see what needs to be done to either
correct (if simple) or archive pages that are so out of date as to be
useless (or worse, misleading).
-- Kevin

confusion.

Post by Nir Lisker
2. Yes. The tutorials [1] are slightly outdated (and SceneBuilder should
disappear from there ASAP and point to Gluon). I don't know who controls
those pages.
3. No. There's not enough traction. Jonathan Giles collects some "links

Post by Nir Lisker
the week" and the semi-zombified /r/JavaFX subreddit is enough to

indicate

Post by Nir Lisker
that we shouldn't invest yet in this direction.
[1] https://docs.oracle.com/javase/8/javase-clienttechnologies.htm
- Nir

Post by Johan Vos
It has been mentioned a number of times that JavaFX would benefit from a
JavaFX website.
1. A set of pages with details on what OpenJFX is, how to build, where