Thank you very much 😄 Agree for a showcase if it can deserve it 😄

Absolutely!

My JPro license was expired. I'm mailing them to see if I can get an extended license.

Ok

Otherwise can a free heroku account be good solution ? I haven't played with Heroku yet, but I think it can't be too mysterious.

@loloof64 The problem is not the hosting itself, I actually own a hosting company. The problem is the license for the software that lets a JavaFX application run through the browser 🙂

Indeed. I've just found a stackoverflow post that confirm that Heroku does not support JavaFX.

Sorry, I haven't well read your post

I got the license extended, but unfortunately it didn't work as expected. I think some JavaFX API's might not be fully supported in JPro yet. I asked them for a list. This is how the UI rendered through JPro:

@User uploaded a file:

It renders perfectly locally of course:

@User uploaded a file:

While we wait, let's have a look at the PromotionDialog. This is the current code:

@User uploaded a file: PromotionDialog before changes

I will try to refactor it now.

Thank you 😄

I'm still a developer without real coding methodology.

Furthermore, unit testing with chess are more complicated according to me than for a traditionnal calculator kata

~~~Do you think that following more TornadoFX style can improve the result with JPro ? Indeed, I just translated many plain JavaFX concepts.~~~(Sorry, this is not an accurate question)

OK, here is a version writtin as a TornadoFX fragment, which can be used together with a blocking dialog. That said, this made me realize that we don't have first class support for JavaFX dialogs, so I will add one. I will post an updated version when it can be used as a dialog.

@User uploaded a file: Rewritten as a TornadoFX Fragment

Some of the savings came from me using a map for the selections. An important takeaway is that I tried to avoid repeating myself too many times, especially inside the button actions. I also use an

objectBinding

that binds to the

imageProperty

of the image view. Now each button just needs to update the

selectedPieceProperty

instead of actually modifying another UI element. That feels much cleaner to me.

I need to put my daughter to bed, will be back to play with dialogs and explain more soon 🙂

Thank you : I read it right now and try to learn from it 😄

@loloof64 This was something that @edvin and i did last year that may help. I'm coming to the project with a lot of Java experience and sometimes overlook the purer approach. https://edvin.town/leveraging-tornadofx-to-the-fullest/

@loloof64 Here is an actual working implementation that you can just swap out, back to using the Dialog API again:

@User uploaded a file: Untitled

@carlw Good idea, we could do that with several parts of this app.

@carlw Thank you 🙂 Going to read it.