Skip to content

Latest commit

 

History

History
84 lines (72 loc) · 7.13 KB

ROADMAP.md

File metadata and controls

84 lines (72 loc) · 7.13 KB
Raw

Roadmap

  • Proof of Concept
  • Prototype
  • WebFX CLI
  • WebFX Demos
  • WebFX Website
  • WebFX Docs
  • WebFX Blog
  • JavaFX
    • javafx-base
    • javafx-graphics ⓵
    • javafx-controls ⓶
    • javafx-media
    • javafx-web
    • javafx-fxml ⓷
  • Language, Build & Runtime Environments
    • GWT
    • Vert.x compatible ⓼
    • J2CL ⓸
    • TeaVM ⓹
    • Kotlin compatible (via J2CL or TeaVM)
    • Scala (via TeaVM only)
    • JxBrowser ⓺
    • WebAssembly (via J2CL or TeaVM)
  • Ecosystem
  • WebFX Maven Plugin
  • Enterprise application prototype
  • Modality (first Enterprise WebFX app)
  • CI/CD pipeline (see example of GitHub workflow)
  • GitHub workflow automatic generation by the CLI
  • Unit test support in WebFX CLI
  • Additional CLI features for contributors
  • Syntax documentation of webfx.xml files
  • Improvement of the OpenJFX patching process
    • Automate the process to ease a rebase on OpenJFX
    • Rebase WebFX on OpenJFX latest version
  • General Availability

⓵ 100% = No 3D, no CSS. JavaFX 3D can't be easily mapped to HTML. For CSS, the WebFX approach is to rely on HTML CSS, rather than emulating JavaFX CSS in the browser. See ⓽ for more info about this approach.

⓶ WebFX supports the general javafx-controls API (allowing you to write custom controls). So far, the supported JavaFX controls are: Button, CheckBox, RadioButton, ContextMenu, Label, Hyperlink, TextField, TextArea, PasswordField, ProgressBar, Slider, ScrollPane, SplitPane & TabPane.

⓷ FXML relies on reflection, which is not supported by transpilers. Alternatively, WebFX could transform fxml files into transpilable Java code. A prototype has been made with this approach using Memory Game, a FXML-based JavaFX game (see working demo).

⓸ An effort is currently being made to make WebFX transpiler-agnostic. J2CL (successor of [GWT][gwt-website] in active development) will be soon supported. This future-proof step will also bring all next goodies from J2CL, such as WebAssembly target (in addition to JavaScript) and Kotlin language (in addition to Java).

⓹ TeaVM is another popular transpiler. Whereas GWT & J2CL are Java-source transpilers, TeaVM is a byte-code transpiler, which will open the door to other alternative JVM languages such as Scala. Also, TeaVM supports Java 21, including record and new switch expressions.

⓺ The JxBrowser support will offer an external web view that developers can use to run, test and debug the web version of their WebFX app directly from Java (no transpilation required!). The IDE will simply run your app with the WebFX Kit runtime (instead of OpenJFX) in the JVM, and the DOM generated by WebFX will be rendered in JxBrowser (a Chromium-based browser controlled by Java). This will considerably speed up the development cycle of web apps.

⓻ WebFX extras provides additional features for WebFX, and simpler alternative controls to the complex JavaFX controls not yet supported (ex: simple data grid and charts).

⓼ WebFX Stack provides additional enterprise-level features such as: UI router, I18n, Validation, Auth(n/z) with SSO support, client-side ORM, DB access, websocket-based event bus (for server communication - focus on Vert.x), and server push features. WebFX Stack + Vert.x is a Java full-stack solution (similar to React + Node.js).

⓽ WebFX CSS relies on dual format: JavaFX CSS & HTML CSS. WebFX developers will need to write both formats. Although it's more work, this is the most optimised approach (emulating JavaFX CSS and loading caspian.css in the browser would be a heavy approach). WebFX CSS will provide a lighter initial CSS for JavaFX that will replace caspian, using a modern sleek minimalistic flat design.

Some redesign work is also necessary to transit from the current patching process (which is mainly a manual patch of OpenJFX 8) to a more professional patching process with tooling allowing regular rebasing onto OpenJFX.