Encapsulation Challenges (Patreon)
Content
A conversation can have a "layout" which is the UI elements, text area, speaker name text area, background, etc. But the layout needs to figure out what it is from a Menu, this way we can re-use the power of the general editor to layout the conversation layout... but the problem is the plugin should not really know what all of that is...
There are many ways around the problem by giving the plugin more knowledge than it should have... but I'm focused on finding a solution that does not do this... somehow...
The benefits vastly outweigh the costs of doing proper encapsulation. *brainstorm hat on*