I've created a tree view extension in qV11 but it takes lot of time to load the data and render while table view with the same data set works fast . Can somebody explain the data loading and filtering process for extensions and how is it different from table view ? How can we achieve faster data loading with extensions ?
A significant difference is that for QV objects the data remains on the server, and only visible data is transferred to the client. In an extension, any data required by the extension is transferred to the client to act upon.
Thanks Rob for your response.Do you have any suggestion to enhance the performance while working with extensions? Is there a way to have some pagination kind of stuffs which will load only part of the data at a time?
Yes, in the definition.xml file (or via script) you set a PageHeight property. This define how "high" or how many rows per page of data you receive. The higher the value the more rows the server has to send to the client.
Thanks Alexander..it should be really helpful .Will try this out . Actually I need to implement pagination for the D3 Collapsible tree view. Where, I want initially to show only 10 children for a particular node with a link which will display the other nodes in the size of 10 .
Hmm, that might be a bit harder as you can't really query a sub-set like that. But if it's a fixed multiplier of 10 I guess you could match the initial page height with nodes X 10
