Fitty Update - The Marriage of User Configs and Immutable Data

  When we think about a workout plan we've got two different sets of information that are carrying alongside one another at the same time. The first is the immutable data of the plan itself.

  A plan, as noted prior, will have a series of workouts, those workouts will contain exercises, those exercises will contain sets, and those sets will contain metrics.

  But here's the thing, for most of these steps we have user configurable data that wouldn't be immutable. A workout plan has a custom name. The workouts consist of exercises yes, but each of those exercises will have metrics saved when the user completes them. We need this because without data tracking we'll struggle to...track data.

  We don't want to include our user configurable data in ScriptableObjects generally because ScriptableObjects tend to be stickier. By that I mean they'll end up holding onto data a bit like a singleton, or any static reference. They'll even hold onto data in between sessions regardless of what scene you jump to. In some cases this is rad as hell, but in other cases it can be really problematic.

  Additionally when you want to save data you can't actually save an SO straight to Odin's system. It gets...upset would be putting it lightly. Just don't do it. We'll use my save and loading interface from the other Moosecat projects, I've already tested this and we are gucci. Ok, cool, Oaf, but when you aren't busy abusing the comma can you tell me what the problem is?

  Well, like so many things in life. Words are hard, I'm trying to think of a good naming convention for these two environments to keep them nice and clean. I think I've come to the following conclusion. Literally as I'm writing this to you, so it might be trash. We'll be learning together.

  Workout Plans, Workouts, Exercises, Sets, and Metrics will all be the conventional DatumNoun system. So DatumWorkoutPlan, DatumWorkout, DatumExercise, and so on.

  Then for all of the Savable data, we'll go with SavableWorkoutPlan, SavableWorkout, and so on. Also, how weird is the word "Savable?" I really feel like English shouldn't have cut the E out of that. It really messes with my Synesthesia.

  This is a minor refactor. I think once this is done I'll be able to start on the Workout Plan GUI. As with everything else I'm just doing something that "works" but isn't the final setup. Honestly we don't know how much data we want to make configurable. Because of that there isn't much I could do now that WOULDN'T be a waste of time.

  Alright, I suppose I better get back to it.