Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>While I fully agree that that is ugly markup, I think using the ugly view syntax to write off ASP.NET MVC as a whole is not fair. The view syntax has gotten the least attention from Microsoft, and I am fully expecting something to be done about it soon. </p> <p>Other answers have discussed the benefits of MVC as a whole, so I will focus on the view syntax:</p> <p>The encouragement to use Html.ActionLink and other methods that generate HTML is a step in the wrong direction. This smacks of server controls, and, to me, is solving a problem that doesn't exist. If we are going to generate tags from code, then why bother using HTML at all? We can just use DOM or some other model and build up our content in the controller. Ok, that sounds bad, doesn't it? Oh yes, separation of concerns, that is why we have a view. </p> <p>I think the correct direction is to make the view syntax as much like HTML as possible. Remember, a well designed MVC should not only give you separation of code from content, it should let you streamline your production by having people who are expert in layout work on the views (even though they do not know ASP.NET), and then later as a developer you can step in and make the view mockup actually dynamic. This can only be done if if the view syntax looks very much like HTML, so that the layout folks can use DreamWeaver or whatever the current popular layout tool is. You might be building dozens of sites at once, and need to scale in this way for efficiency of production. Let me give an example of how I could see the view "language" working:</p> <pre><code>&lt;span mvc:if="ViewData.Model.ShowPrevious" style="float: left;"&gt; &lt;a mvc:inner="ViewData.Model.PreviousPost.Subject" href="view/{ViewData.Model.PreviousPost.Id}"&gt;sample previous subject&lt;/a&gt; &lt;/span&gt; &lt;span mvc:if="ViewData.Model.ShowNext" style="float: left;"&gt; &lt;a mvc:inner="ViewData.Model.NextPost.Subject" href="view/{ViewData.Model.NextPost.Id}"&gt;sample next subject&lt;/a&gt; &lt;/span&gt; &lt;div mvc:if="ViewData.Model.ShowNextOrPrevious" style="clear: both;" /&gt; </code></pre> <p>This has several advantages:</p> <ul> <li>looks better</li> <li>more concise</li> <li>no funky context switching betwen HTML and &lt;% %> tags</li> <li>easy to understand keywords that are self-explanatory (even a non-programmer could do this - good for parallelization)</li> <li>as much logic moved back into controller (or model) as possible</li> <li>no generated HTML - again, this makes it very easy for someone to come in and know where to style something, without having to mess around with Html. methods</li> <li>the code has sample text in it that renders when you load the view as plain HTML in a browser (again, good for layout people)</li> </ul> <p>So, what exactly does this syntax do?</p> <p>mvc:inner="" - whatever is in the quotes gets evaluated and the inner HTML of the tag gets replaced with the resulting string. (Our sample text gets replaced)</p> <p>mvc:outer="" - whatever is in the quotes gets evaluated and the outer HTML of the tag gets replaced with the resulting string. (Again, sample text gets replaced.)</p> <p>{} - this is used for inserting output inside of attributes, similar to &lt;%= %></p> <p>mvc:if="" - insde the qoutes is the boolean expression to be evaulated. The close of the if is where the HTML tag gets closed.</p> <p>mvc:else</p> <p>mcv:elseif="" - ...</p> <p>mvc:foreach</p>
    singulars
    1. This table or related slice is empty.
    1. PODoes anyone beside me just NOT get ASP.NET MVC?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRedFilter
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou could fairly easily implement exactly what you're describing as your own view engine and ditch the WebForms solution entirely.
      singulars
      1. PO
      1. USJ Wynia
    2. COi was going to make a note that there are other view engines available, and also that I think a cf-style markup would work well, which is what you are showing here.
      singulars
      1. PO
      1. USTracker1
    3. COThanks for the info, was not aware there were other view engines.
      singulars
      1. PO
      1. USRedFilter
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload