DataGrids and JavaScript--A Slippery Slop
After reviewing a few of the rich client-side grid components, my client has decided on Infragistic's UltraWebGrid2. This is actually a very nice component that helps my client keep the look-and-feel of the desktop applications we're converting to ASP.NET. But as we all know, there are no silver bullets when using the browser for presentation--in the end it's all HTML and JavaScript.
There are a ton-o-hooks for client-side JavaScript within this component, and I was hoping to avoid most of them. But when you're 99% there (in your client's view), and you can tweak the presentation with just a little client-side script, what the heck--go ahead and step back into that all to familiar world of JavaScript.
So what if there are no compile time errors; you'll discover run-time failures. It takes a real man to embrace a language who's syntax and semantics' change based on the run-time client's browser.
My point? I started to add "just a few" of those features that required JavaScript... you can guess where that is heading. I'm going to make a major pitch to my client within the next few days to end this madness. My feeling is that client-side script will produce a very rich user experience; but, the script should be generated by components, not by the application programmer.
More on this later.