UPDATE: THE SURVEY HAS FINISHED.
One sentence that I hear quite frequently when discussing JavaFX with other developers is that JavaFX “does not do XYZ” or “does not support XYZ”. Often they list features that are indeed available in other technologies / frameworks. To get a better understanding of these “missing features” I thought it would be good to create an online survey and to collect them. Ideally we end up with a complete list and ideally we have the perfect UI framework if we can check off every single item on the list. 🙂
[…] Survey: JavaFX 8 Missing Features […]
Binding from FXML to Controllers, at the moment, one can only bind the entire control / node via fx:id or a control’s action via #action. Would be great to have it also binding properties like text=”${person.name}” where person is a model object on the controller
Please do not use the comment section for your feedback. Follow the link to the survey.
Canvas/GraphicsContext needs to be updated to support rendering every bit as well as Nodes. A couple of things I’ve noticed missing are in Text (integer font metrics to allow smoother rendering) and in Image (we need a nearest-neighbor rendering mode to prevent blurring on hi-dpi displays). It would also be nice if WritableImage could provide a GraphicsContext.
@Jeff Martin Please do not use the comment section for your feedback. Follow the link to the survey.
the link to the survey doesn’t work anymore
Yes, the survey has finished. Thanks for pointing this out, I have updated the blog.
What was the result of the survey?
Haven’t found the time to post the results, yet. Will do next week.
[…] I take it as a good sign that the categories “Performance” and “Quality” have not seen a lot of submissions in the “Missing Features Survey”. […]
[…] the last post of the Missing Features Survey series I said that this post would be about missing features in CSS and FXML. Now it turns out that […]