.NET MVC feed Reproduces jQuery UI
I've seen several blog posts and tutorials on View Mixing in jQuery and UI Elements for Views in a .NET MVC Web Application. But they usually target developers with a thorough understanding of the full dev cycle and variations in back / mid-level technologies.
As a front-end developer, I only draw jQuery UI for third-party developers only - it warns against a non-web forms interface to increase code maturity.
I'm trying to throw away "ok ... this is your pattern ... is this rudimentary for MVC? No logic in the view? I read that this is" server-side stuff. "You are just serializing the properties I ask for, or better. .. let me easily know what you can send me ... I can implement the interface via jQuery UI. "
So how valid is my position?
Can jQuery grid be expected to handle at least the bottom 85% of inline .net control (low-powered capacities # from strings)?
How about online editing? ... from the grid?
Will running exclusively in web services make your life easier? and if so, isn't that a logical way to build a .net-to-jQuery relationship? - ajax bind twixt server (.NET WS methods) and client?
mny thanks --steve ...
a source to share
If this is an admin interface and the client has agreed that users must have javascript enabled, I think using javascript to create widgets on the page is a better option than using ASP.NET controls. If, however, it is a public website, I would say that a clean html and css approach is much better, then use javascript to improve the page gradually!
Now I do not recommend using asp.net server controls because they spit out bad markup and are too complicated to use. Instead, I use jQuery to do the nagging work and polling the dom and passing through. I also don't recommend using jQuery UI because they are missing some very important widgets like no data, no tree, etc. I know there are many jQuery plugins out there, but they are not components and so every plugin has to reinvent the wheel to achieve whatever it takes. Once you've included all your plugin and css libraries, you often end up with a very large page size. Also each plugin often has a different home page and documentation, which may or may not be up to scratch.
I think the best UI library is YUI and you can easily combine it with jQuery. Since each widget is made up of core components, the total download weight is less. Also you have all the documentation in one place with 100 working examples. It also means working with the same set of javascript templates across the board, so you learn more about the library with each widget. Hopefully the jQuery UI catches up, but personally I'm looking forward to YUI 3, which for me could mean jQuery's downfall altogether ...
a source to share
Don't fight the platform. Thus, pain and suffering.
MVC view objects are vastly different from asp.net web forms with server controls - you get straight up the html. You get jquery and ajax mostly for free, with (almost) magical server-side handling of the ajax call.
They are designed to do what you ask. Writing your own jquery ui reinvents the wheel.
It's not only a ton of extra work, but also a payoff. You would be the only developer trying to do this, and when you needed help, few could offer advice.
a source to share
jQuery is a very mature library. It is used by thousands of people across the internet and I don't think I have ever encountered a bug. YUI feeds on YAHOO, so this is also a battle tempered.
One thing I didn't tell you about is that I'm using the default web form viewer with asp.net mvc. I think this is still the best option since you are getting intellisense and also the Resharper refactoring even searches your views, and anaylsis static solution can find code errors in your views.
I used MvcContrib Fluent Html to create my markup, but you can also check out this article , which was very DRY protected.
a source to share