#What causes this warning can it be ignored?
1 messages · Page 1 of 1 (latest)
<@&987246487241105418> please have a look, thanks.
why are you using javafx stuff in swing?
and the warning is kinda unrelated to the filechooser
it is related to the java module system
and you probably use javafx in a non modular application which most likely causes this warning
because swings default file chooser is awful and doesn't use windows native file chooser
because I didn't make the application I just wanted to add a proper filechooser to this project which is based on swing
https://github.com/Lordszynencja/Charter
I see
You need to make correct module configuration
how bad would it be if I just ignored it since it's just a warning
and just porting the whole project to javafx would probably be a task for several hundred hours of work
it works until it doesnt anymore
classic one with any warning that u ignore
obviously u cant leverage the benefits of a java module if u don't use it correctly. so ur final app that u deploy to ur customers via jpackage will be much larger than it could be
yeah it is some work, but it seems like that project consists mostly of swing independent logic, you dont have to rewrite the whole project
but it is recommended imo
are you the project owner though?
no
I think with some combined effort it could be possible to port it
looks like an interesting project to port to javafx ngl
you know if the owner would be interested in that though?
the project requires some refactoring in general tbh
like some image files arent even in the resource folder where they should be
also the packaging is using batch files instead of proper configuration with build tool
I would just attempt to do it on my own I asked them about it and said it would take too much time