User (Old forums)MemberMay 29, 2007 at 9:54 amPost count: 23064
Are there any plans to support column vrtualization? Currently the grid asks for every column whether they are on screen or not.
Imported from legacy forums. Posted by Bill (had 5526 views)User (Old forums)MemberMay 29, 2007 at 10:13 amPost count: 23064
Could you describe your usage scenario and explain why that feature would be important for you?
Imported from legacy forums. Posted by Pascal (had 457 views)User (Old forums)MemberMay 29, 2007 at 11:10 amPost count: 23064
We are currently trying to port from an environment where the grid only asks for data when the user scrolls it into view. This is useful for us because the data that is being displayed is usually not stored at the client, it is retrieved via a service request. Having to retrieve all the data whether it is being viewed or not would be wasting trips to the service. This causes the grids inital load to be slower if there are many columns, and also puts a strain on scrolling.
This seems to be standard behavior with the various winforms grids we had used in the past including the DataGridView object that comes with .NET. The infragistics WPF grid does not handle column virtualization either (as far as I can tell) …
We are basically doing R&D with WPF trying to get a handle on what we can and can’t do with the various controls that are out there. Any information about whether this will be supported in a future release would be helpful.
Imported from legacy forums. Posted by Bill (had 407 views)User (Old forums)MemberMay 29, 2007 at 1:31 pmPost count: 23064
What you describe is a feature we call data virtualization, which would make the grid “ask” for data (rows and columns) only as they are needed.
This is something that we plan to do, but I don’t have an exact schedule for that feature yet.
Imported from legacy forums. Posted by Pascal (had 433 views)User (Old forums)MemberJune 19, 2007 at 7:56 pmPost count: 23064
Could you explain how data virtualization is different from UI virtualization which is claimed to be supported on Help/Features page:
Supports UI virtualization, even when grouping data, so only elements currently in view are created and kept. Provides faster loading time, uses less memory.
Imported from legacy forums. Posted by Sergey (had 428 views)User (Old forums)MemberJune 20, 2007 at 8:51 amPost count: 23064
UI virtualization means that the UI “containers” are not created for every single data item in the data source, but rather only for the items that are currently visible in the viewport of the data grid.
Data virtualization means that the data source collection does not need to be completely loaded into memory for the data grid to use it. Instead, there would be APis by which the data grid would ask the application to provide the data items as they are required.
UI virtualization is a standard WPF mechanism used by the ListBox, ListView, etc… It is important because without it, you could end up with a huge visual tree for an ItemsControl that is bound to a large collection.
Data virtualization is useful in situations where the application has to display a huge amount of data and does not want to pre-load all that data into memory (in an ObservableCollection, for example) in order to display it in a data grid.
Imported from legacy forums. Posted by Pascal (had 568 views)User (Old forums)MemberJune 20, 2007 at 3:18 pmPost count: 23064
Pardon my ignorance, I’m still learning WPF… But it seems to me that data virtualization can be achieved by providing the collection with “fake” members, which are created but do not load their data until the data are requested.
Of course, this wouldn’t solve the problem if all data are actually requested at once, even before they are shown. Does the grid works this way?
Imported from legacy forums. Posted by Sergey (had 330 views)User (Old forums)MemberJanuary 22, 2008 at 1:54 amPost count: 23064
What is the status of the Virtualization support for the Xceed Grid ?
We expect to have up to 10.000 items of information and without this we cannot use the Grid.
Also, can you support virtualization for other View, like album cover view, carousel, … ?
Imported from legacy forums. Posted by viewon01 (had 383 views)Odi [Xceed]SpectatorJanuary 22, 2008 at 10:56 pmPost count: 426
There’s no data virtualization in any Q1 2008 release, but when there is, this capability should work no matter which view you use. As for UI virtualization, that’s already being performed by the grid.
Imported from legacy forums. Posted by Odi [Xceed] (had 6451 views)
- You must be logged in to reply to this topic.