From the rules:

Scripts that have any of the following will be auto-rejected:
...
-Scripts that use anything from JavaFX

 

Why did yall decide to ban javafx? I used it in scripts long ago and it worked nps?

I think there might have been some issue loading css for scripts on the SDN, but that isn't enough reason to reject scripts that use javafx altogether. 

Is there another reason that it was banned?

 

Edited November 19, 20187 yr by Mysteryy

2 hours ago, Mysteryy said:

From the rules:

Scripts that have any of the following will be auto-rejected:
...
-Scripts that use anything from JavaFX

 

Why did yall decide to ban javafx? I used it in scripts long ago and it worked nps?

I think there might have been some issue loading css for scripts on the SDN, but that isn't enough reason to reject scripts that use javafx altogether. 

Is there another reason that it was banned?

OSBot is written using swing, makes sense to keep using swing in scripts.

Can't use FXML/ CSS on the SDN so there's really not much benefit to using JavaFX anyway.

Some Java versions don't come with Java FX, and would mean more annoying bug reports from clueless users

1 hour ago, Explv said:

OSBot is written using swing, makes sense to keep using swing in scripts.

Can't use FXML/ CSS on the SDN so there's really not much benefit to using JavaFX anyway.

Some Java versions don't come with Java FX, and would mean more annoying bug reports from clueless users

 

First reason isnt really a good one imo. You can have a jfx application thread and a swing thread living together in harmony. 

Second reason is pretty much the only one I could imagine, but you can still style fx other ways so that's annoying but not a show stopper.

Last reason is also not really a good one either. Its been bundled in java 8 which has been around for a while now. 

 

The only real reason I can imagine is because oracle announced that it wont support it past 2022 in being bundled with java. Then it will be a separate lib.