|
|
Comments and Discussions
|
|
 |

|
You got my 5, since it is a good piece of work, but I ahve some comments:
- As input elements are used in MVC in conjunction with input models, I am really missing all the other overloads, that input renderers have in MVC library, especially those with ...For.
- An inconvenience is the usage: @Html.Html5().andsoon. The convention about these helpers functions is that they are extension methods. You break this convention. If you want to avoid conflicts with future official html5 support, I think you better use your on namespace, rather than extend the legacy one, and introduce an uncommon element in the notation.
- As you mentioned, html5 introduced the several semantic elements and the custom support element also. It would be useful to have such helper also (like MvcForm and FormExtension), ex: @using (Html.Element("nav")) {..., or even specialized, templatabable elements for nav, section or others
- And I am really interested why you needed those interfaces. I suggest you consult the source of ASP.NET MVC a little bit, and see what conventions they used.
But all these don't make your work less appreciable. Keep up the good work! I am really interested in future updates.
|
|
|
|
 |
|
|
General News Suggestion Question Bug Answer Joke Rant Admin
|
Class Library for HTML 5 controls for ASP.NET MVC
| Type | Article |
| Licence | CPOL |
| First Posted | 6 Aug 2011 |
| Views | 67,596 |
| Downloads | 4,799 |
| Bookmarked | 127 times |
|
|