OOP as a coding style is... clunky. The pain that I experienced on Pascal, which was acceptable to the generation before me, is a pain that modern developers (I suppose) suffer when they see this. this. this. (You get the joke.)
Unfortunately the Java is strong in this one and I still use "this" etc. I always forget the new modern way even after reading a few JS books.
I'm looking to create objects using references like these:
- https://gist.github.com/benpriebe/55b7e950b5e9d056b47e
- https://fek.io/blog/crockford-objects-in-java-script/
Today's code update shows an uncooked definition of Actions or Skills, an abstraction of buttons that users can click to get the counter going up. I'm still figuring out how to do this with an eye for importing jsonc files of Skills and SkillTargets (direct object of the verb).
On the design side, I wrote the story and wound up with something more concerned with the logistics and transportation of cargo, so I'll be adjusting skills and actions in line with that.
Merge in question with horrible separation of concerns: https://github.com/s-santillan/thelastline/commit/b19370ecd80953728f89b0be32cc7fbc8b3d6f7b
