Hello, loves! The new scheme for Content seems to be working out well. Remaining are two concerns … Well, I say two, though there are surely many things to be concerned about. The two I have in mind are: The upcoming Content items require “instance variables”, such as the cycling flag and time counter for the Animated item, that are not included in the standard batch. We’d like to make them optional. The upcoming items need to be subscribed to some events. We need a way to represent those without adding code to the Content class. I have at least two options before me for the additional variables: In Python we can always just store new items as if they were already there, albeit with a bit of complaining from PyCharm. Or we could pass in a little package, say info, of named variables and access it indirectly self.info.cycling. The second of these would leave the Content item nearly immutable, and if we moved state inside one of these info things, it could be entirely immutable. I’m not…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.