Why not MS Ajax... Good question. I think it was originally designed to use with WebForms (even if it has lots other of capabilities).
Anyway, jQuery, Prototype, ExtJS are very mature ones and has lots of extnetions plug-ins etc. And they are open-source which brings more ability to it, more people contribute to it.
MVC Contrib is going to want to give people the option to use whatever library they want
This is good idea, but there is always something "by default". Everybody can write bunch of helpers, even separate projects for any client-side library.
But it would be nice to decrease such a need providing a good "default".
abombss
Every library, ext, prototype, jquery, can all do pretty much the same stuff just a little differently
Yes. But you also understand that they do it different ways. I don't believe it's possible to write GridHelper that would produce the grid with the same functionality for ExtJS, jQuery, Prototype.
abombss
Anything that isn't common you probably want to be writing custom JS for by hand anyway.
Probably yes. But Helpers could just make it easier, like FormHelper does.
abombss
My question is, what type of helpers are you thinking of that are so tied to a particular library.
All is because of losing WebForms controls. So I think about having UI helpers that would allow doing things like these:
Grids. Filtering, grouping, sorting, paging etc. Very good in ExtJS.
Inputs. Calendars, date picker, formated text, time picker, currency etc.
User interaction. Modal windows, tooltips, feedback messages, progress bars etc.
Validation.
Consistent style.
etc
Generally the idea is to "replace" existing suites as much as possible. ExtJS seems for me to be the closest one to large components suites, like
Telerik's.
Maybe it is not about Helpers, but rather user controls...
Another vote for ExtJS featuring in mvccontrib, Microsoft MVC tutorials and the like. I love its BasicForm and TextField components to allow easy client-side validation. I think these rich javascript libraries are easily a replacement for ASP.NET control
libraries.
I share this opinion. Helpers are helpers, not ServerControl replacements.
Ok. It sounds logical. So let's assume that we want to create server controls to "connect" functionality of client-side libraries with the server part.
What should be done for that and what are the plans in the MvcContrib about that?
I mean MVC is cool. But it's a really a bad thing to lose current WebForms controls.
nagir
Member
162 Points
184 Posts
Re: Helpers for client-side libraries
Dec 21, 2007 09:27 AM|LINK
Why not MS Ajax... Good question. I think it was originally designed to use with WebForms (even if it has lots other of capabilities).
Anyway, jQuery, Prototype, ExtJS are very mature ones and has lots of extnetions plug-ins etc. And they are open-source which brings more ability to it, more people contribute to it.
But MS AJAX should probably be considered too.
nagir
Member
162 Points
184 Posts
Re: Helpers for client-side libraries
Dec 21, 2007 09:45 AM|LINK
This is good idea, but there is always something "by default". Everybody can write bunch of helpers, even separate projects for any client-side library.
But it would be nice to decrease such a need providing a good "default".
Yes. But you also understand that they do it different ways. I don't believe it's possible to write GridHelper that would produce the grid with the same functionality for ExtJS, jQuery, Prototype.
Probably yes. But Helpers could just make it easier, like FormHelper does.
All is because of losing WebForms controls. So I think about having UI helpers that would allow doing things like these:
Generally the idea is to "replace" existing suites as much as possible. ExtJS seems for me to be the closest one to large components suites, like Telerik's.
Maybe it is not about Helpers, but rather user controls...
Regards,
Dmitriy.
andyfreestyl...
Member
171 Points
56 Posts
Re: Helpers for client-side libraries
Dec 21, 2007 10:20 AM|LINK
Another vote for ExtJS featuring in mvccontrib, Microsoft MVC tutorials and the like. I love its BasicForm and TextField components to allow easy client-side validation. I think these rich javascript libraries are easily a replacement for ASP.NET control libraries.
abombss
Member
575 Points
164 Posts
Re: Helpers for client-side libraries
Dec 21, 2007 06:50 PM|LINK
I share this opinion. Helpers are helpers, not ServerControl replacements.
I hope to prove you wrong then... Although as noted above, I don't think a GridHelper is the correct use of a helper, but we will see.
nagir
Member
162 Points
184 Posts
Re: Helpers for client-side libraries
Dec 23, 2007 12:35 PM|LINK
Ok. It sounds logical. So let's assume that we want to create server controls to "connect" functionality of client-side libraries with the server part.
What should be done for that and what are the plans in the MvcContrib about that?
I mean MVC is cool. But it's a really a bad thing to lose current WebForms controls.
Cheers,
Dmitriy.