@agbottan Yeah, the map creator generates several files from the black/white border image. The main one is the polygons.txt which specifies the boundary points for each territory. It also generates a centers.txt and place.txt. I think you are probably better off generating the black/white border image then using the existing TripleA map creator to generate the necessary files. Otherwise you probably will end up having to recreate much of that tool. Here is the map documentation: https://github.com/triplea-game/triplea/blob/master/docs/map_making/map_and_map_skin_making_overview.md#sec_2
how feasible is this? We have years of technical debt, let alone splitting all logic from swing. This could be a 2-5 year project. Is it worth it? Is there a larger migration strategy? Arguably the loading screens a much smaller lift then the rest of the game.
The general launch and other "utility"/navigation screens are probably the easiest things to migrate because they can easily get rebuilt from scratch in comparison to the other stuff.
The main game rendering is going to be a challenge though. We can't easily re-use existing logic, because JavaFX requires an approach, that's a little bit more object-oriented. I have a high-level concept that makes use of this really nicely by turning all of the elements on the screen into literal objects with on click listeners so that we don't need to implement this logic on our own anymore.
what is the proof of concept for dynamic JavaFX UI components? Being able to create UI components programmatically is important. I don't think we'd want much to any FXML for the game proper.
Currently working on the launch screen, which is mostly dynamic. Using FXMLs only expresses java code in a different format and keeps the code shorter, so you can view an FXML as a more complex Node where only the assigned controller can access the inner nodes directly. Like any other Node you can embed it somewhere, or embed other nodes in it.
The only thing to keep in mind is that the current system is only prepared for singleton-like nodes, so if we wanted to use a node multiple times, we'd have to extend the current loading mechanism a bit.
The biggest problem with using a "global email" is that if we did that without any authentication, one could use our service to spam another ones email account and create something like a dos attack.
So in any case we'd need authentication, which might defeat its purpose already.
Thank You Triplea
Couldn't find the previous thank you thread so...been a while and just wanted to say I really appreciate what redrum, Roix, Dan Van Atta, ssloff ( haven't seen you in a while hope all is good ). You guys been kicking ass.
Thanks to prastle, panther, cernel, hepps and well... there's a whole bunch of you
Thanks for making triplea cool. It makes a few people happy and they then make more people happy
Rock On TripleA