Hello Dear
Maybe its not the right forum, but I didnt find a general Discussions Part in ASP Forum. Feel free to move.
I just have to say something that really really disappoints me on Infragistics for Web. It's the HTML that most of the components spit out.
The one thing that really screws me up is your heavy use of tables, even If you dont have to (maybe I don't see something). But in general, it just destroys layout, or the ability to.
For example the Websplitter control. The most outer element is a DIV (would be fine) but, you just put a table, with table body, tr and a td in it.
Now, if I tell this splitter-component to have Height="100%" in markup, the resulting HTML is the DIV with 100% (ok) but then the inner-table (in the div) has fixed absolute height which you are going to calculate (sometimes wrong calculated).
I know the reason why you are calculating the Tables and TD heights, because IE or maybe other browsers to do really mess up Tables when you use percentage for sizing. If you would not use tables, you would not have to calclute sizes, would not mess up with the box model, performance would be better, and everyone would feel fine.
Can you tell me the reason why all of your ASP.NET Control designer love to do stuff in tables? And is there any planning of doing it not in tables?
Completely agree with this sentiment and Infragistics probably do as well as they've been producing light weight controls.
Cheers, Rob.