Sorry ... wrong thread ...
Am 22.09.20, 10:18 schrieb "Christofer Dutz" <[email protected]>: So I took it to the Flex list and heard some in favor mails, but not a single negative one .... so I think it would be safe to continue. Chris Am 22.09.20, 10:09 schrieb "Carlos Rovira" <[email protected]>: Hi Hugo, comment in line: El lun., 21 sept. 2020 a las 23:53, Hugo Ferreira (<[email protected]>) escribió: > > What means keeping the grid position when the data is changed by a sorting > !? > If you scroll the inner data when you reorder you reset the scroll to top, since in fact you removed the data and recreated. With actual solution the scroll is not touched and you keep at the point you were after sorting. > But I understand that there are different visions and approaches. > > My only concern it's performance. > I have a few limit grids (I haven't got there yet with my Flex port for > Royle to do a test, but I hope to get there as soon as possible) with many, > many rows (when I say many, I mean thousands) and sorting it's very > important but also the performance while sorting. Users are used to wait to > load to many records but after the data is loaded from the server, sorting > is something that happens on the client side super faster. > performance will be better in the current solution since we are not removing all data and recreating it. But you're really talking about other problems. When you have thousands of rows, is a different problem. In flex we had virtual layout (remember "useVirtualLayout" property?). In Royale is the same but instead of having that functionality "baked" into the component we have other beads and in Jewel we have "VirtualList" and "VirtualComboBox", still not "VirtualDataGrid" in place, is something to be done in the future. Since VirtualList and VirtualComboBox seem to already have some issues, I thought it was better to left VirtualDataGrid for when the other two are better polished. So as in Flex, the "virtual" versions only create renders for the visible items/rows and then, as you scroll up and down the items are filled with the right data to visualize, recycling the renderers instead of recreating them. If you're going to need this, you probably should start testing List vs VirtualList and see how you see that. I think trying to solve any issue you find there will make more easy to work in a VirtualDataGrid with VirtualDataGridColumns (as you can see the pieces are all setup and doing that VDG should be very easy) -- Carlos Rovira http://about.me/carlosrovira
