使用替代视图引擎有哪些好处？

发布于 2024-08-10 11:00:45 字数 806 浏览 5 评论 0原文

我正在使用 ASP.NET MVC，发现有一些可用的替代视图引擎，例如 NHaml 和 Spark。我的问题是为什么您要使用备用视图引擎？我不认为拥有这样的东西有什么好处：

<ul if="products.Any()">
    <li each="var p in products">${p.Name}</li>
</ul>
<else>
    <p>No products available</p>
</else>

使用 Spark 视图引擎（自从那以后，我还没有使用 Spark 来验证这一点，并且可能完全错误，因为你通过了，所以你不会得到 Intellisense代码作为字符串）以及：

<% if products.Any() { %>
    <ul>
      <% foreach (var p in products) { %>
        <li><%= p.Name %></li>
      <% } %>  
    </ul>
<% } else { %>
    <p>No products available</p>
<% } %>

使用内置的 ASP.NET MVC 模板格式（尽管我承认悬挂的大括号非常难看）。除了不喜欢“gator”标签（或悬挂的大括号）之外，是否有任何合理的理由考虑使用备用视图引擎？或者只是因为它是新事物而很酷？

原文

I am playing with ASP.NET MVC and I see that there are a few alternate view engines available for it such as NHaml and Spark. My question is why would you use an alternate view engine? I don't see a benefit to having something like this:

<ul if="products.Any()">
    <li each="var p in products">${p.Name}</li>
</ul>
<else>
    <p>No products available</p>
</else>

using the Spark view engine (doubly so since, and I haven't used Spark to verify this and might be totally wrong, you wouldn't get Intellisense since you're passing the code as a string) and:

<% if products.Any() { %>
    <ul>
      <% foreach (var p in products) { %>
        <li><%= p.Name %></li>
      <% } %>  
    </ul>
<% } else { %>
    <p>No products available</p>
<% } %>

using the built-in ASP.NET MVC template format (although I admit the dangling curly brace is pretty ugly). Is there any legitimate reason apart from not like the "gator" tags (or dangling curly braces) to consider using an alternate view engine? Or is it just cool because it's something new?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

半﹌身腐败 2024-08-17 11:00:45

尝试让它变得更复杂一点：

<div if="orders.Any()" each="var order in orders">
  Here's your order #${orderIndex+1}:
  <ul>
    <li each="var p in order.Products">
       ${pIndex}: ${p.Name}
       <span if="pIsLast"> (the end)</span>
    </li>
  </ul>
</div>

我可以在这里看到流程。我实际上可以在这里看到HTML。现在看看：

<% if (orders.Any()) { %>
  <% var orderIndex = 0; foreach (var order in orders") { %>
   <div>
    Here's your order #<%= (orderIndex+1) %>
    <ul>
      <% int pIndex = 0; foreach (var p in order.Products) 
         { bool pIsLast = pIndex == products.Count; %>
        <li>
           <%= pIndex %>: <%= p.Name %>
           <% if (pIsLast) { %>
              <span> (the end)</span>
           <% } %>
        </li>
      <% ++ pIndex; } %>  
    </ul>
   </div>
  <% orderIndex++; } %>
<% } %>

我在这里迷路了。那里有 HTML 吗？

对我来说，这是主要原因。当然，Spark 提供了大量的功能 - 宏（在 Spark 标记中编码 Html.Helpers）、PDF 导出等 - 由其他人列出 - 但作为一名程序员，我更喜欢干净的代码。

再举个例子，你经常使用 for (int i = 0; i < products.Count; i++) { Product Product = products[i]; 吗？ .... } 这些日子？您更喜欢 foreach (var products in products) {} 吗？我会的。不仅是因为打字更少。因为：

它更好地表达了意图，
读起来更好，
它隐藏了额外的细节（例如 .Count、.Length 或 .Count()；或者如果它是 IEnumerable，你必须以特殊的方式遍历），
它减少了我疲惫的头脑中的数量。变量使上下文混乱（以及我疲倦的头脑），
因此我可以专注于问题，没有任何事情
可以帮助避免 {}，因为不需要在内部有一个变量 - 减少行数
以及当您从 IList 更改集合时到数组，你不需要到处改变 50 个循环

，这就是像 foreach 这样简单的事情。每个原因都很简单，但它们概括起来却有更大的意义。这些原因完全适用于 Spark。嘿，看起来我恋爱了;-)

更新：现在，你知道吗？查看我的帖子的编辑历史。我不得不多次编辑该死的 ASP 代码，只是因为我遗漏了一些地方。我只是不知道这是对还是错。如果我在那里有跨度，或者有条件的话，它是完全隐藏的。

更新：嗯，又一个编辑...将 ASP 的 if/span 移到 li 中...

Try to make it a bit more complex:

<div if="orders.Any()" each="var order in orders">
  Here's your order #${orderIndex+1}:
  <ul>
    <li each="var p in order.Products">
       ${pIndex}: ${p.Name}
       <span if="pIsLast"> (the end)</span>
    </li>
  </ul>
</div>

I can see the flow here. I can actually see HTML here. Now take a look:

<% if (orders.Any()) { %>
  <% var orderIndex = 0; foreach (var order in orders") { %>
   <div>
    Here's your order #<%= (orderIndex+1) %>
    <ul>
      <% int pIndex = 0; foreach (var p in order.Products) 
         { bool pIsLast = pIndex == products.Count; %>
        <li>
           <%= pIndex %>: <%= p.Name %>
           <% if (pIsLast) { %>
              <span> (the end)</span>
           <% } %>
        </li>
      <% ++ pIndex; } %>  
    </ul>
   </div>
  <% orderIndex++; } %>
<% } %>

I'm lost here. Is there any HTML there?

For me, this is the main reason. Of course, Spark gives TONS of features - macros (where you code your Html.Helpers in spark markup), PDF export, etc - listed by others - but as a programmer I prefer clean code.

As another example, do you often use for (int i = 0; i < products.Count; i++) { Product product = products[i]; .... } these days? Would you prefer foreach (var product in products) {}? I would. Not only because it's less to type. Because:

it expresses the intent better
it reads better
it hides additional details (like .Count, .Length, or .Count(); or if it's IEnumerable that you have to traverse in a special way) from my tired mind
it reduces number of variables cluttering the context (and my tired mind)
thus I can concentrate on the problem, nothing goes in the way
it helps to avoid {} since there's no need to have a variable inside - reducing line count
and when you change the collection from IList to array, you don't change 50 loops all over the place

and that's about such simple thing as foreach. Each reason is simple, but they sum up to something bigger. And these reasons apply perfectly to Spark. Hey, looks like I'm in love ;-)

Update: now, you know what? Look at my post's edit history. I had to edit the damn ASP code several times just because I missed some bits here and there. I just do not see if it's right or wrong. It's completely hidden if I have the span there, or condition at place.

Update: hm, yet another edit... moving ASP's if/span inside li...

回复收藏 0 原文