Traveller System Update 31 - Orbits Part 2

Got to adding the UX (User Experience) for entering the data from the various charts in Book 6, pages 44-45. I've essentially combined all those charts to single chart. 

Edit and creates have nice drop-downs and the index seems decent enough.

Dropdowns!

Charts!

I do realize when reading what other people do when creating Traveller software that I am doing this in an entirely different direction. I'm coming from the viewpoint that the user may have a different physics or using more up to date info than the Scouts Book 6. This application is very, very heavy on allowing the users to edit and maintain all those tables.

Is this a good approach? Not really - people just want to use the stuff without having to deal with all that under the hood stuff. However, there are plenty enough applications out there for most of this, and all with a much better interface. My personal interests have always been in what we call the backend for software: the databases and internal business logic. Which is great for some things, and not so great for others. 

Regardless, this is my approach for this. In theory, of course, someone could write another application using the very same database that this system maintains. Why I chose SQLite to externalize the DB versus hardcoding all these values was to allow other applications access. Again - that's how I've always worked in the past: the DB is entirely independent of the application. Had one job where I mostly wrote microservices, and they all interacted with the same database. I'll also note the repo is under the MIT open-source license, so people can do whatever they want with the software.

Anyway, I'll have to finish adding all the data, then I can actually calculate the planetary orbit! I think - I may have missed something else but Ill cross that bridge when I get there.

And my next post will probably be the expected Corsairs recap, along with notes about why we are switching to the Dolmenwood game as an experiment.