Hi
I am using RadGrid 2008 Q2.
I find that the client-side databind of the grid is extremely well done. We are now doing far less postbacks to the server and because we do everything we possibly can on the client we are gaining a far richer user experience.
I have 3 questions:
1. I have noticed that if we start with a blank grid it defaults to loading 10 empty rows. This is far more when using a hierarchy as it seems to load an extra 5 rows for each master row. As such it can start with 50 rows!
Is there a reason for this?
Presently on the server when the page loads I bind to a dummy class object of just 1 row.
This way I have reduced the HTML response from 117Kb down to 50Kb.
Are there any implications to this? I haven't noticed anything break by taking this approach.
2. When adding items to the grid it all works nicely.. until I add an item past the initial HTML markup. E.g If I start with the default 10 rows, the 11th row is shifted to the right and the data is in all the wrong columns.
This happens as it seems the first 10 rows respect hidden (not invisible) columns but the 11th row onwards does not (in fact it will show the hidden columns).
A further consequence of this is that the hierarchy column (+/-) no longer shows.
How can I avoid this?
3. I couldn't find any examples for a hierarchal grid. At the moment I bind my detail grid in the RowDataBound() client event as it seems that the detail view doesn't automatically fire like it does on the server.
E.g.
if(e.get_item().get_owner().get_name() === 'VenueDetails') //MasterView
{
var tableView = sender.get_detailTables()[e.get_item()._itemIndexHierarchical];
Kind regards
Mark Eaton
I am using RadGrid 2008 Q2.
I find that the client-side databind of the grid is extremely well done. We are now doing far less postbacks to the server and because we do everything we possibly can on the client we are gaining a far richer user experience.
I have 3 questions:
1. I have noticed that if we start with a blank grid it defaults to loading 10 empty rows. This is far more when using a hierarchy as it seems to load an extra 5 rows for each master row. As such it can start with 50 rows!
Is there a reason for this?
Presently on the server when the page loads I bind to a dummy class object of just 1 row.
This way I have reduced the HTML response from 117Kb down to 50Kb.
Are there any implications to this? I haven't noticed anything break by taking this approach.
2. When adding items to the grid it all works nicely.. until I add an item past the initial HTML markup. E.g If I start with the default 10 rows, the 11th row is shifted to the right and the data is in all the wrong columns.
This happens as it seems the first 10 rows respect hidden (not invisible) columns but the 11th row onwards does not (in fact it will show the hidden columns).
A further consequence of this is that the hierarchy column (+/-) no longer shows.
How can I avoid this?
3. I couldn't find any examples for a hierarchal grid. At the moment I bind my detail grid in the RowDataBound() client event as it seems that the detail view doesn't automatically fire like it does on the server.
E.g.
if(e.get_item().get_owner().get_name() === 'VenueDetails') //MasterView
{
var tableView = sender.get_detailTables()[e.get_item()._itemIndexHierarchical];
// Bind detail to grid
tableView.set_dataSource(e.get_dataItem().EventMisc);
tableView.dataBind();
}
Is this the correct approach? I'm not comfortable with it as I am using a protected member: _itemIndexHierarchial.
Kind regards
Mark Eaton