I'm working on an enhanced grid (similar to https://github.com/Knockout-Contrib/KoGrid) that may require several thousand rows to be rendered. The grid has many features like inline-editing, column resizing, row-level actions, etc. Initially I began with nested foreach looks to generate the rows/columns knowing it would eventually become a bottleneck.
I'm at the point where I would like to improve this approach. I've thought about rendering the grid in memory much like this plugin does but I'm worried about the level of control I can get on the individual nodes and bindings.
My research brought me to your 2 plugins, knockout-table and knockout-repeat. I've looked at the source of each and I understand their differences. My main question however is how do they compare to each other in terms of performance and usability?
The knockout-table should be faster in theory but is it worth the maintenance cost?
I'm working on an enhanced grid (similar to https://github.com/Knockout-Contrib/KoGrid) that may require several thousand rows to be rendered. The grid has many features like inline-editing, column resizing, row-level actions, etc. Initially I began with nested foreach looks to generate the rows/columns knowing it would eventually become a bottleneck.
I'm at the point where I would like to improve this approach. I've thought about rendering the grid in memory much like this plugin does but I'm worried about the level of control I can get on the individual nodes and bindings.
My research brought me to your 2 plugins, knockout-table and knockout-repeat. I've looked at the source of each and I understand their differences. My main question however is how do they compare to each other in terms of performance and usability?
The knockout-table should be faster in theory but is it worth the maintenance cost?