I think you are misunderstanding the MVC pattern a bit.
One of the purposes of MVC pattern is to divide your application into "layers".
- The Model-layer which contains "data"
- The View-layer which represents the "data" (the Model)
- The Controller-layer which handles user input and modifies "data" (the Model)
The Model does not tell the View how the data should be presented.
The View interpretes the Model and presents the data.
This means that the Model may contain information about how data the may be presented by using properties or fields. But ultimately it's up to the View.
In your case (for example) you may add the property –
Model.DisplayFooName. But this in itself will not change how your View looks because the View has not been altered. Your Model has a shiny new property that your View may use to change the way the data in your Model is presented. In essence the Model is powerless when it comes to the View. Your View decides how your Model-data should be presented, and you cannot make changes only to your Model, to change the way the data is presented in the View.
Ultimately, changes to your Model cannot change how View decides to present data in it.
To tackle the actual problem:
If you have a global setting to toggle the display of your
FooName, you can create a
HtmlHelper to speed up the process of toggling it. Instead of having to write something like...:
... every time you want to toggle it,
you can create helper that allows you to just simply write
HtmlHelper contains the model-data.
This could be sped up by using Find & Replace.