Episode #125 of the Stack Overflow podcast is here. We talk Tilde Club and mechanical keyboards. Listen now
3 Added a link to the Stategy pattern so people can read up about it
source | link

Have you considered using a Strategy patternStrategy pattern? You would have one View class that contains the common code & routines called by several views. Children of the View class would contain the code specific to those instances. They would all use the common interface you created for the View, and thus the differences would be encapsulated & coherent.

Have you considered using a Strategy pattern? You would have one View class that contains the common code & routines called by several views. Children of the View class would contain the code specific to those instances. They would all use the common interface you created for the View, and thus the differences would be encapsulated & coherent.

Have you considered using a Strategy pattern? You would have one View class that contains the common code & routines called by several views. Children of the View class would contain the code specific to those instances. They would all use the common interface you created for the View, and thus the differences would be encapsulated & coherent.

2 just saw I had written 'object' where I meant 'class'
source | link

Have you considered using a Strategy pattern? You would have one View objectclass that contains the common code & routines called by several views. Children of the View objectclass would contain the code specific to those instances. They would all use the common interface you created for the View, and thus the differences would be encapsulated & coherent.

Have you considered using a Strategy pattern? You would have one View object that contains the common code & routines called by several views. Children of the View object would contain the code specific to those instances. They would all use the common interface you created for the View, and thus the differences would be encapsulated & coherent.

Have you considered using a Strategy pattern? You would have one View class that contains the common code & routines called by several views. Children of the View class would contain the code specific to those instances. They would all use the common interface you created for the View, and thus the differences would be encapsulated & coherent.

1
source | link

Have you considered using a Strategy pattern? You would have one View object that contains the common code & routines called by several views. Children of the View object would contain the code specific to those instances. They would all use the common interface you created for the View, and thus the differences would be encapsulated & coherent.