Inconsistent package structure in the samples.

[Naoghuman]

Inconsistent package structure in the samples.

• Some projects have package, other not.
• It's a anti pattern to use the default package.
• All sample projects should have the same base package structure (also the cli samples).

Info:
https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html

[jperedadnr]

I'm aware of this, but only the samples under the HelloFX main category are the ones without package.

These samples were initially the only ones available in the Docs, meant to do a quick start with JavaFX 11. The focus is on the class itself, and how you can compile it and run it, not in the project structure, package names or other usual conventions.

Adding a hellofx package (for instance), will lead to the same exact samples we have under the CommandLine category. But maybe that's ok? It will still match the Docs structure.

[Naoghuman]

Sure it's okay. When we look the most samples are similar. We have over 20 samples and when momentary some are equals then is that okay from my view of sight.

What are the goals from these examples? The examples should show how to do the specific topic in JavaFX with different build tools or with the command line or ... .

From my personal view the samples should not only show the specific topic, also the best practice how to do it in JavaFX 11. So we need later also additional commentary, JavaDoc and the license in the samples, but thats are points for another issue.

[Naoghuman]

So the question is should the package structure for the HelloFX project updated or not?
If yes we need then also an issue in openjfx/openjfx-docs for the update from the links in the guide.