Coding 2022-10-05
All right, let's see... I completed a round of renaming, but I still want to work through more.
Right now, I'm trying to figure out what to name two internal and low-level classes, because the current names are really unintuitive.
Basically, one class represents, I guess, the ambient state of a single run of MOTR, relating the registry, a reporting interface, the results, and a reference to each running task. Later, it'll have a stream multiplexer attached to it.
That class uses another class as a helper. The point of the helper class is to wrap a bunch of helpful boilerplate around the execution of a task; this makes it easier to write task classes or functions, because there's no reason to change this behavior, so third-party (ish) code shouldn't be responsible for implementing it.
I ended up calling them Execution and Step, and renaming some internal classes. The results are leaps and bounds beyond what there was before, which were the same names as related, but completely different classes elsewhere in the application. (Some of those classes were also renamed, but just making the name unique wasn't enough.)
That's some good work for today, but there are many more passes to do. Before I move around, I should probably work on beefing up the documentation here to make sure I still like the names after I've tried to really use them.
Anyway, it's late and I want to wrap up for tonight, so...
Bye.
Good night.