Replies: 3 comments 3 replies
|
Hi Gary, The risk today is that you'd have to build everything from the ground up (core and plugins) and continue to do so until we post a release. I must confess I'm spending more time these days working with JReleaser than Griffon. I hope I can come back to it before the end of the year. |
|
Thanks, Andres. Perhaps I'll use Griffon 2.16 instead. Then I can either use JDK 8 with JavaFX (and even GroovyFX, I guess) or I can use Swing instead of JavaFX. In the case of Swing I have a question I haven't been able to find an answer to. JDK 8 is the minimum requirement for Griffon 2.16, but what is the maximum? Will Griffon 2.16 with Swing work with JDK 17? Thanks again. P.S.: is Griffon 2.16 compatible with Groovy 3.X? |
|
Thanks. Let me explore one more thing before deciding on my approach. Would you prefer that I not try Griffon 3 with JavaFX 17? If I were to try v3 I might have many questions since the doc is obviously incomplete. I also might identify issues/bugs that I would have to report and hopefully get some answers. I'm thinking you don't have time for any of that at this point! I'm guessing there really isn't anyone else actively working on the project. |
Uh oh!
There was an error while loading. Please reload this page.
I'd like to try Griffon, but I need JavaFX 17 support. I see that is coming in version 3, which seems to be in "pre-release." How risky would it be for me to use the github development_3_X branch at this point?
--Gary Kopp
All reactions