By Jove,

Hello, loves! By Jove, I think he’s got it! We’ll find out. Also: design documentation. Results: very favorable. I took some time last night to think about our content objects and created this design document: ! I’m sure that’s entirely clear, but just in case, we’ll be finding out what it means over the next few sessions, if in fact it means anything. Key notions that doing that scribbling brought to mind: Pass desired subscriptions to the content constructor as data, event name, caller id, and a callback. Do all the subscriptions in the Content __init__ or in a separate initialize method built into Content class, looping over the provided subscriptions. Provide a changed method in Content, publishing the standard message that signals the view to update. (This may turn out to be more tricky than it seems, but I’m sure we can do it.) Express whether to allow entry as a function, probably a lambda. Possibly default to something reasonable, possibly to state == len(resources). (Won’t…