Code Style Rules

OpenJFX has strict code style guidelines that should be enforced on every changeset. All developers will differ in opinion on every coding convention (tabs or spaces?). However on a large project with many individuals, if it were left to each developer to specify their own conventions, then we would quickly end up with a complete mess for our source code. This extends far beyond spaces vs. tabs (which, by the way, we use spaces) but also includes API design and is one reason why all API must be reviewed before it is integrated. Consistency is vitally important in making an API easy to learn and use.

...

Not everybody will like all of the code style rules, but hopefully most people will like most of them. More important, by following these rules we will have a consistent codebase with all the aforementioned benefits. This is a "living document" and will be amended as we go along. When new issues arise, we will add them to this list.

Whitespace

1. No trailing whitespace. Most (all?) IDEs can be configured to automatically trim trailing whitespace
2. Use Spaces not Tabs.
3. Use 4 space indentation
4. Keep the single empty line at the end of every file
5. Insert a space between the Copyright notice and the package statement
6. Insert a space between the package statement and any import statements
7. There should be one space between the last import statement and the class documentation
8. ...

Code Review Process