Friday, February 09, 2007

Syncfusion GridControl vs GroupingGrid

I am starting to write the grid abstraction for my client-side framework. Developers will code to a "virtual grid" API, and there will be adapters for the actual implementations of the grids (Syncfusion, Infragistics, WinForms, DevExpress, etc).

Because most of Wall Street uses Syncfusion grids for trading apps, this is the first adapter that I need to write.

Syncfusion has 3 different grids: the regular old GridControl, the DataBoundGrid, and the GroupingGrid. The grouping grid is used a lot in my place to provides rollups of data. You would think that the GroupingGrid would inherit from the GridControl, but unbelievably, it does not. The API sets are not even consistent.

I have spent my time using Lutz Roeder's very excellent Reflector to try to hunt and peck through the Syncfusion class hierarchy in search of the various classes and functions in the GroupingGrid that implement the same functionality as the GridControl. The fact that I am dealing with two incompatible API sets has increased my work by 100%.

C'mon Syncfusion ... you should know better than that!


©2007 Marc Adler - All Rights Reserved

2 comments:

chris said...

My palz are in syncfusion hell presently. I am trying to figure out how much pain it will be to rid us of the syncfusion problem. My main issue is that you need to use an alternate grid API for anything heirarchical!!! DUMB!!! So - the question is how far do you go trying to bend syncfusion before you throw it all away...

-CD

Michel said...

Somewhere you think that the different grid providers could go together and define an open grid api that all of them support so it would be easier to switch/use different grids if you dont use extensions. Its all to frustrating with all those apis.