饲养.NET MVC意见jQuery UI的方式 [英] Feeding .NET MVC Views the jQuery UI way

问题描述

我已经看到了一些博客文章和教程overviewing jQuery的混合并在.NET MVC Web应用程序视图的UI元素。但通常针对的充分开发周期和回/中间层技术变化的COM prehensive把握开发者。

I've seen a few blog posts and tutorials overviewing mixing in jQuery and the UI elements for Views in a .NET MVC web app. But usually targeted at developers with a comprehensive grasp of the full dev cycle and variations of back/middle tier technologies.

由于前端开发者，我投球一个jQuery只UI到后端开发 - 他提醒对非web表单接口，为code成熟POV的缘故

As the front end developer I'm pitching a jQuery-only UI to the back-end dev - he cautions against a non-webforms interface for sake of the code maturity pov.

我试图还击*嗯......这是你的格局......是不是要元素MVC吗？没有逻辑的看法？我读的是服务器端的东西你刚才序列我所要求的，或更好的性能...让我轻松地找到你的可以给我...我就可以实现通过jQuery UI的用户界面。的

I'm trying to hit back with *"well...it's your pattern ...isn't it elemental to MVC? No logic in the view? I'm reading that to be 'server-side stuff'. You just serialize the properties i'm asking for, or better...let me easily discover what you can send me...i'll be able to implement the UI via jQuery UI."

因此​​，如何有效的是我的位置？

So how valid is my position?

能否jQuery的电网预计至少处理.NET的原生控制的底部85％（行低到中等容量＃）？

Can jQuery's grid be expected to handle at least the bottom 85% of .net's native control (low-to-moderate capacities # of rows)?

如何在在线编辑？ ......从电网？

How about in-line editing? ...from the grid?

应该只在Web服务的工作简化自己的生命呢？如果是这样，那不是建立一个.NET到jQuery的关系合乎逻辑的方式？ - 阿贾克斯liaisoning变成往返服务器（.NET WS方法）和客户端

Would working exclusively in Web Services simplify his life at all? and if so, wouldn't that be logical way to build a .net-to-jQuery relationship? - ajax liaisoning twixt server (.net WS methods) and client?

MNY THX
--steve ...

mny thx --steve...

推荐答案

如果这是一个管理界面，并在客户端已经同意，用户必须启用JavaScript的话，我想用javascript在页面上构建小部件是一个更好的选择比使用asp.net服务器控件。但是，如果这是一个面向公众的网站，我会说，一个纯HTML和CSS的做法要好得多，然后用javascript逐步提高新的一页！

If this is an admin interface, and the client has agreed that users must have javascript enabled then I think using javascript to build widgets on the page is a better option than using the asp.net server controls. If however this is a public facing website I would argue that a pure html and css approach is much better, and then use javascript to progressively enhance the page!

现在我不主张过使用asp.net服务器控件，因为它们吐出的标记很差，他们过于复杂的使用。相反，我一直在使用jQuery做繁重的工作和DOM查询和穿越。我也主张不使用jQuery UI，因为他们缺少一些非常重要的部件，例如，没有数据表中，没有树视图等。我知道有很多插件的jQuery但他们不是组件化，因此每个插件需要的车轮，以重塑实现这一目标需要的一切。一旦你已经囊括了所有你的插件库和CSS，你最后往往具有非常大的页面上的足迹。也各插件通常具有不同的主页和文件，可能会或可能不达到标准。

Now I dont ever advocate using asp.net server controls, because they spit out poor markup and they are overly complicated to use. Instead I have been using jQuery to do the grunt work and dom querying and traversing. I also dont advocate using jQuery UI because they are missing some very essential widgets, for example no datatable, no treeview etc. I know that there are lots of plugins for jQuery but they are not componentised and therefore each plugin needs to reinvent the wheel to achieve everything it needs. Once you have included all your plugin libraries and css you often end up with a very large page footprint. Also each plugin often has a different home page and documentation that may or may not be up to scratch.

我认为最好的UI库是YUI，你可以用它轻松jQuery的结合。因为每个插件从核心部件由下载的总重量更小。你也需要在一个地方与工作的例子100的文档。此外，它是指用同一套全线JavaScript的模式工作，因此与每个插件您了解图书馆越来越多。希望jQuery UI的将迎头赶上，但我个人很期待YUI 3这对我来说可能意味着完全放弃jQuery的...

I think that the best UI library is YUI, and you can easily combine it with jQuery. Because each widget is made up from core components the overall weight of download is smaller. Also you have all the documentation in one place with 100's of working examples. Also it means working with the same set of javascript patterns across the board, so with each widget you learn more and more about the library. Hopefully jQuery UI will catch up, but personally I am looking forward to YUI 3 which for me might mean dropping jQuery altogether...

这篇关于饲养.NET MVC意见jQuery UI的方式的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！