Java implementation for communication between launch monitor(s) and the GS Pro software.
At this point this is just a playground for JavaFX and Spring, playing around with the idea of getting my SLX working with GS Pro so I can give it a go.
Couldn't end up reverse engineering the Bluetooth communication from the SLX/Tittle devices. In the mean time, the guys at SLX released the SLX Connect GSPro integration, which works reasonably well, so this project is not being deprecated. It was still a pretty fun project to get some Spring/JavaFX experience under my belt.
Api is defined at GSPro Open Connect V1. The client provides interfaces and classes to be used within:
- Connector Api Data
- Launch Monitor (Provider)
Client used to connect to and communicate with the GSPro Open Connect V1.
DEPRECATED
At this point the client is just an added layer which isn't needed. I've left it in there (deprecated) incase it ends up getting used by something else. But the same functionality has been implemented in the gspro-app project using FX properties to allow for status updates.
Java FX application (spring boot backed) providing the interface for the GS Pro and Launch Monitor management. The application is pretty straight forward:
Select one of the launch monitors you have installed and click the Connect button. Things should be relatively smooth after that point.
- Implement the heartbeat thread to continually check on GS Pro
- Start adding a couple sample launch monitors
- Implement the Launch Monitor Properties screen
Provides the shot history.
This is not based on the shot actually being successful (just that it was attempted). If it was a valid launch monitor shot and just wasn't picked up by GS Pro, you'll still want to be able to access thtat data.
- Add export functionality to the Shot History
Simple two directional logging, incase anything goes down and you need to look at what's up.
- Add export functionality to debug log
Feel free to throw any suggestions or fixes my way:
- Fork
- Branch
- Develop (VSCode)
- Pull request
Development is done within a devcontainer and hopefully keeps things super easy. When building the devcontainer the post build step will run mvn install -DskipTests. Once this is completed you'll most likely have to restart the Java Lanuage Server.
Java development and devcontainers seems to be a little finicky. But once it's up with the Java Language server going, it's pretty slick.
