Menu
Here's my problem:
I am disturbed by the "impedance mismatch" between what graphic/web designers actually produce, and what is needed by the standard ASP MVC view engine.
Basically there is no way to visually design a view i.e. the output of an action. No WYSIWIG designer. The only way to go from a static HTML design to an MVC app is by manually translating, and all the pain that brings.
What I have been dreaming of reccently is a view engine + designer tool that would let designers actually do their jobs, and for it to "just work" in the web app.
Something like what Blend does for WPF.
Yes, we had something similar in Web Forms but that had its own limitations and I still don't reckon it was usuable by most designers.
Surely a view engine + designer tool could be written, perhaps using a strict syntax (no abitrary code in templates), and allow the designer tool to mock your typed views and render dummy data for visualising output. And for designers to design an action - and have the tool indicate or breakdown the various visual elements on screen (sub views etc).
347
View Engine is responsible for rendering the view into html form to the browser. ASP.NET MVC includes two different view engines, the newer Razor View Engine and the older Web Forms View Engine.
ASPX or Web Form Engine is the default view engine for ASP.NET that is included with ASP.NET MVC from the beginning itself. The syntax used for writing a view with the ASPX View Engine is the same as the syntax used in the ASP.NET web forms.
As you know MVC is highly extensible hence you can completely replace the Razor view engine with a new custom razor engine.
There is a rumour that Expression Web will support MVC...
115
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
