If yo are not familiar with the concept MVC. It's about 3 parts:

• Model: Its usually the object responsible for read from the database and handle the data

• Controler: Thats the main code object, that contains all the functions and code needed to parse, filter or convert information from the Model to the View, like... the intermediate.

• View: Finally the view, the artistic part, the UI, the final product, thats usually free of code, just invoque Controllers methods and or variables

Imagine that you have a Client screen, that shows the usual data on a list. But that web can be seen in PC, Mobile Landscape, Mobile Portrait and Tablets. You cant have the same design for every screen, as the proportions are different, and the size of the screen too, so you cannot fit all the PC info in just a Phone screen. So then you talk about "responsive". 

This MVC allows you to keep the same code as you only need 1 Model and 1 Controller, but you can have as many Views as you need or want. That is the point i was looking to include in Unreal Engine

I did not needed a Model, because i was not reading any database, so i removed that from the idea, i wanted to focus on Controller and View. Unfortunatelly in Unreal, Widget is both Controller AND View, and that was a major wall to avoid.

As long as Widgets are "just" objects, you can create a class for example WBP_C_Configurator and add all the functions, variables and code you need, and the create a child of that class, like WBP_V_Configurator_Landscape and WBP_V_Configurator_Portrait, those two as sons of the main class, have all the code, functions and variables from parent. So now you can design all you want on those childs, and just call what you need from the parent class, and have a View free from code, and ONE Controller with all the code, that does not be affected by views. It was perfect, just what i wanted and it was really easy to implement.