the hard part of this comic chat toolkit project now is figuring out how to factor and organize the classes so that it's easy to use and makes sense, but because I didn't engineer the format there's a lot of work in just re-reviewing the code so far and deciding how to refactor the code so that it breathes well without creating limitations that I might be unaware of, because I don't control the data format at all.
In writing this code, I've so many times realized that two things I thought were separate (or more accurately: could not prove to be identical) were actually related and could be refactored as their own lil' thing. I am still finding things like that over a year later.
The main code file has shrunk considerably as a result, but it's still 1400+ lines right now and I am really trying to figure out a way to split it in half and have some ideas, but it's getting kind of hard to audit how "messy" each split would really be because so many bits of this code are so tightly interrelated.
this is, to me, always the hard part about publishing code. It's no problem writing it, but re-organizing it into nice logical units that are easy to follow along with, understand and modify is another skillset almost entirely.