We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date

Quick summary of difference between Model and Binder?

I have looked through the user guide, forums, KB, class reference, etc. and can''t seem to get a feel for this difference. Can you please summarize the difference between the Model and the Binder properties on the GridDataBoundGrid? From reading various posts here, I can see there are different times to use properties and events in each, but can''t put my finger on why they are separate objects. Thanks.

1 Reply

AD Administrator Syncfusion Team June 16, 2004 12:49 AM UTC

Hi Dan, the way the Model and Binder are separated is just becuase of the way things did evolve. In the beginning the design was planned such GridDataBoundGrid has a regular GridModel and the idea was that the binder could be plugged into the model with a 1-1 relation and we could continue to use the regular grid model and have databinding logic be separated into the GridModelDataBinder class. In later versions we found out that we also have to derive the GridModel and that users need to be able to customize the binder. So we derived a GridDataBoundGridModel and made GridModelDataBinder public. GridDataBoundGridModel has only a couple of overrides. The bulk of the implementation is in the binder. A clean solution would be to have the GridDataBoundGridModel provide properties that then get redirected to the binder. We do that for more important properties, but for less common scenarios you have to use the binder directly. Stefan

Live Chat Icon For mobile
Up arrow icon