I find that many of the complex M$ controls are implemented in an inelegant way that makes them almost totally useless. The grid control in .NET is infuriating to use, even though it does a vast amount of stuff "for" me it almost never does what I want it to do. For one, it fails to give me adequate CSS stylesheet control over its extraordinarily ugly default appearance. It is also really hard to extend the grid control with clientside scripts.
On the other hand, I do like the .NET Table objects because they give you a very powerful metaphor for building and modifying HTML tables. You can build up tables in a variety of ways, and then pass the built-up table to other code that adds additional functionality on the client and server sides. It makes for a lot of code reuse and data/interface flexibility. The table objects are thankfully elegant and simple which is why they are so useful, unlike the bloated grid control.
What is nice is about AjaxPro is that it handles the serialization of complex data for you so you can build functions that work on both sides very efficiently without a lot of really complex code. I also like it because it works.
When Microsoft talks about all of this stuff that they are going to be doing for me in Atlas, I worry about it being yet more bloatware. The new Atlas stuff isn't even really released yet, either. I may take a look at it when it is more mature, but so far the AjaxPro stuff works just fine for me.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/ajaxpro
The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info/
Don't forget to read my blog at http://weblogs.asp.net/mschwarz/
-~----------~----~----~----~------~----~------~--~---
