SubClass a View?

in MVC does it make sense to have a View Base Class and have subclasses of it?
What does the base class look like in Xojo a WebContainer?

I think it makes more sense to design an API via a Class Interface so you can hide the details of the view, and even swap out different classes (Window, Container, Panel) and not have to change the rest of your code. You would implement the details in a subclass, of course, which would contain your “standard” code and then create instances with specific code for each context you use them in.