I am creating a handful of Grids in MVC. I notice that Document.Ready is called pretty quickly but the ig.loader takes quite a while.
In FireFox this is an issue because it is taking longer than 10 seconds for the grids to render.
The Razor code executes quickly. Other than changing the design of the page to create everything in javascript, instead of creating the grids in MVC, is there anyway to control when the infragistics code takes a breather to avoid the script running to long message?
At this point it looks like the databind call,
I am wondering if converting it to call back into my controller via a GridDataSourceAction, or a WebService would help.
Do you have any suggestions, or samples to point me to?
I have been able to call back into the controller, I believe that will solve the problem
Unfortunately the MVC Render method and what is associated with it is just taking a very long time when I have a lot of grids.
I have had to remove the MVC code and put it in javascript where can create a grid every so often so as not to stop the browser from being unresponsive
Even putting up a loading message is frustrating when trying to create 30 grids and it takes several minutes
Hello ddally,
Thank you for the update. You have to remember with 30 grids even if you have 10 cells in each that is over 300 elements that will have to be rendered and have styles applied. Do you require all the grids on this pager? Can any be moved to another page that displays when you operate a grid or other control to get the details you want to see?
Sincerely,Mike P.Developer Support Engineer IIInfragistics, Inc.www.infragistics.com
unfortunately the Hierarchical grid did not work in the situations we needed it, mostly due to the fact that any child selections were cleared as soon as you selected other child selections and the designer did not like the layout of it.
I pushed back but this is what they chose so now I have to live with it. If I could get the hierarchical grid to keep child selections across multiple child rows that might have worked .
Because of the number of grids I have converted the MVC into javascript and just start drawing one every x ticks and that at least keeps the browser reponsive.
Thank you for the update. I have a few follow up questions concerning this matter. How many records do you have in each grid? Have you considered implementing paging on the grids?
http://help.infragistics.com/NetAdvantage/jQuery/2012.2/CLR4.0?page=igGrid_Paging.html
Looking forward to hearing from you,
Generally I only have 2 - 3 records per grid. I have a set of maybe 30 - 40 physicians in a hospital with each being assigned a handful of patients.
Moving to javascript/html only was not that difficult, in fact I find it perhaps a better way to keep full control of the calls I am making. I have some improvement to do but the javascript version is not manageable, only because I can keep the page responsive because I am in control of when I created each grid.
Yes,
Moving away from the MVC model allowed me greater control and solved the problem I was having.
Thanks,
I am following up to see if this matter has been resolved. If this isn’t the case please let me know what questions you have concerning this matter.
Please let me know if I may be of further assistance with this matter.
Thank you for the update. I am glad to hear that using JavaScript for the igGrid is working for you. Do you have any further questions concerning this matter?
Sorry had a typo -- It was supposed to say -- javascript version is NOW manageable