Post #3637425

revisiting the source of kinopy, I'm realizing that I should abstract a bit more with my Provider concept the fact that these theatres aren't using Veezi's B2B offering anymore does not mean my Veezi code should be thrown away, and the new Tapos provider code I will write should be usable for multiple theatres. so I should write the Provider classes per-vendor when possible, and then instantiate them with theatre-specific data (URLs, API keys, etc.) the Provider classes for theatres where I'm scraping the HTML probably have to remain ad-hoc though. Most of the possible code re-use there is already in place